Acrobat 8.1 update fails under Vista

I don't have a solution, but I'll add that the exact same thing is happening with Acrobat 8.1 update on a Windows XP-SP2 PC. I'm also open to suggestions. Thanks.

The problem persists. Every time the Adobe updater runs, I get the 8.1 update and it always fails. It's really quite annoying because this is the update that supposedly provides "[s]upport for Microsoft® Windows Vista™ (32-bit and 64-bit versions)". It's also a waste of time.

*** SOLUTION *** (at least for me)

I downloaded the patch and ran it manually. During the process, there were 5 errors. I selected "retry" for each. The process succeeded. This seems a bit too much like black magic for my taste, but it worked.

The errors:

Error 1310. Error writing to file C:\config.msi\4d4257.rbf. Verify that you have access to the directory. (Retry) (Cancel)
Error 1310. Error writing to file C:\config.msi\4d427a.rbf. Verify that you have access to the directory. (Retry) (Cancel)
Error 1310. Error writing to file C:\config.msi\4d43d1.rbf. Verify that you have access to the directory. (Retry) (Cancel)
Error 1310. Error writing to file C:\config.msi\4d4721.rbf. Verify that you have access to the directory. (Retry) (Cancel)
Error 1310. Error writing to file C:\config.msi\4d4879.rbf. Verify that you have access to the directory. (Retry) (Cancel)

The other fix for this is to uninstall Reader v8.0, then download & install a fresh v8.1.

I have had good luck on my XP platform. BUT continue to get errors on VISTA platform. Tried uninstralling/reinstall, etc. No luck.

I get ...

'Missing PDF Maker Files
Do you want to run installer in repair mode.'

Does not matter what I select it does not work. Meanwhile, back on the XP. Frustrating as this is a new full cost A 8!

Microsoft Office automatically disabled your PDFMaker macros when you updated to 8.1. To manage your Disabled Items list in a Microsoft Office application check out this thread:
[url]http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=844[/url]

Same problem with 8.0 Standard under Vista. Tried to re-enable PDFMaker macros in MS Office Powerpoint, but there were no disabled items listed. So, stuck again.

Acrobat 8.0 isn't certified under Vista only 8.1. Do your macros show up in 8.1?

Thanks. I can't say now as I have removed Vista and returned to XP. Everything, including Acrobat 8.0 and an update to 8.1, is now fine.

Hi, Adobe guys you should be more careful about this problems. Users are suffering I hate paying for software and ending with a machine reinstallation cause Adobe wouldn't reinstall. DO you care about us enough? Remember Microsoft is at you now...
SOLUTION I USED IS DIFFERENT BUT WORKED:
My installation is x64 Vista with SP1
1. Disable the UAC Control.
http://www.howtogeek.com/howto/windows-vista/disable-user-account-control-uac-the-easy-way-on-windows-vista/
2. Every time the error appears clic retry (every time is a different file).
3. Reboot the system.

I have spent the last couple of days trying to install Adobe Photoshop CS4 on
a dual core Vista 64 system. I was receiving the dreaded message about
c:\config.msi not accessible. Search of the web revealed this occurs
regularly durnig various installs and many have "cures" revolving around
elevating priviledges, etc. I tried all the various suggestions and kept
failing - at least 25 or 30 times.

My experience was that it hit randomly during the somewhat long install
process of CS4. While some installs just keep going anyway, CS4 does not.
The config.msi folder stores rollback info during the install process. If no
rollback is required, I would assume that the files stored there are
unnecessary. Those installs that merely post the error and continue seem to
be OK. CS4 won't do that.

I decided that whatever the bug was, it was a "race" condition of some sort,
so I decided to slow my system down by running other things during the
install. Ultimately I had two videos and the Process Monitor utility going,
and the install finished successfully.

This is why the bug appears randomly across the universe - it is dependent
on system speed and clearly exascerbated by multiprocessing configurations.

I hope this is helpful to those of you who find this post by searching the
web, as I did.