🚀 go-pugleaf

I'm having an updater problem too, and no internet proxy issues here.

I thought the problem was because I'm trying Windows 7 beta, but after seeing this thread I'm not so sure.

I have CS3 on Windows Vista 32-bit, and that has had updater problems of its own. But what I'm concerned with here is a virgin Windows 7 64-bit install--same computer, different physical hard drive. (I'm doing this mostly so I can try out Photoshop CS4 64-bit on a 64-bit OS.) So far, the ONLY Adobe program I've installed is Reader 9.

And now the Updater is trying to update itself - that is, update these files from v.6.0.0.1452 to v.6.0.0.1471:

C:\Program Files (x86)\Common Files\Adobe\Updater6\Adobe_Updater.exe
C:\Program Files (x86)\Common Files\Adobe\Updater6\AdobeUpdaterInstallMgr.exe

However, it fails. If I try to run a 'check for updates' manually from within Reader, the updater crashes and I get a Windows crash message ('updater has stopped working'). If I allow automatic update checks and it tries to run from the system tray, the updated versions get downloaded but then throw up a message about a folder being LOCKED (without specifying which folder they're talking about), and just get stuck in an endless loop, even if I try to change download location preferences.

I have examined the permissions of the folders listed above and nothing seems amiss.

I did manage to fish out the updated files themselves from my download temp cache folder, but I can't just place them in program files. Even if I elevate privileges and Windows allows me to do it, they would no longer match Adobe's certificate files in there.

There maybe be some registry permissions involved as well, but I don't know where to check and frankly this is too much of a wild goose chase. I'm trying to find out whether my next purchases of Phshp and Windows should be 64 bits; that's time-consuming enough as it is. I cannot spend hours trying to hunt down Reader Update-the-Updater problems, although I assume the updater problems would extend to other Adobe products.

So...is this a Windows 7 issue? If so, Adobe is off the hook, for a while anyway, though there are now MILLIONS of Windows 7 beta users.

If this is an Adobe Updater issue, it wouldn't be the first time, and they can't hide behind the 'free software' issue, because Updater problems plague every high-priced version of Creative Suite. And on Mac, too.

Can it be so difficult for Adobe's presumably qualified engineers to work with Microsoft and Apple and iron out update security and permissions protocol glitches?