Great hint. The number of problems with adobe updater has just been reduced by one. 1,653,453,245 to go.

P.S.: Technically, FileVault cannot be called the culprit. adobe updater is the culprit. FileVault is the thing we can act on to work around this particular problem, since there is no way adobe is ever going to fix a single bug in updater.

P.P.S.: This is not an attack on the hint author. We need such workarounds since the only other solution is for Apple to rewrite Mac OS X from scratch around adobe updater, which is a little bit, but not much more likely to happen than adobe fixing the damn thing.

I'm sure adobe updater makes inappropriate assumptions about the system setup, causing this issue. I don't given Apple a total pass though, because encryption should be transparent, and filevault is not. In some cases tasks have to be executed differently on filevault systems, and this pretty much guarantees compatibility problems. Apple really needs proper full disk encryption.