I'm trying to get all relevant topics in the forum updated to help folks know why they having trouble with the update. It's not the additional features, those have been tested with enterprise and paying customers week over week for the past year, it's switching file management to use the WP FileSystem API at the suggestion of WP core developers, which is simply not working out obviously. Because W3TC creates files, if *anything* goes wrong with file management, the user's experience is going to be terrible… obviously. Other plugins don't have to worry about this at all, which the reason why this is so bothersome to users. Making a server faster requires changing it's behavior, there's nothing I can do differently especially with millions of possible environments to deal with.
So I'm sorry for the trouble, but the intent was to do things the "WP Way" and have everyone benefit from what the core developers have learned over the years. We will continue to work behind the scenes to that end, but for the moment the updated releases are reverting activation and file management BACK to the way things worked just fine before, once done, the great new features will work just fine for you.
For those with MaxCDN as a CDN provider, issues there are with their updated API. For those with Cloudflare, issues there arise from updates to their new API (you know have far more control of your account from within W3TC and better integration with their platform).
Thanks for trying W3TC, if there were a simple way create files and folders via PHP in a secure way on every single server and environment out there then clearly we would take that route. If we hadn't have tried to follow recommendations, no changes to install, activation, update etc would have been made and people would stop calling us names… maybe.