Salta al contenuto principale

Resolved: Update 6571 fails

Thread needs solution

Follow-up:

Sorry for going off prematurely. I rebooted my system, ran AIT, and the update went through successfully. It was that simple.

After what support put me through last time, I had no idea it would be that easy.

-----

Update 6571 fails to install. The message is a generic access error. It happens at the very end of the update process.

I had this exact same problem with the 6569 update. I had to completely uninstall ATI, run the cleanup tool, and import my previous backups. Since not all of the settings come back, it was tedious to get everything working.

What gives?

Why is this happening. Is there any easier fix than scraping ATI off my system, getting the full version from support, and rebuilding everything?

0 Users found this helpful

Jerry,

I am going to step out a limb here a bit and make an educated guess as to what is up with your woes with upgrading, others I am sure may run into the same issues.

I suspect you are running Windows 10 and you have not changed the default Power configuration settings?  If yes or if you have made changes you are using the default Fast Startup feature of Windows 10 which is enabled by default?

I suspect as well that you practice a Shutdown of your computer each day and only on rare occasion do you Reboot the computer instead of Shutdown of the machine?

If any of the above rings true, you are using the Fast Starup feature, you need ot know that Fast Starup in Windows 10 is now a form of Hibernation and is invoked when a user chooses to Shutdown the machiune.  A reboot does not trigger Fast Startup and thus is more like the old shutdown method except the machine restarts.

This Fast Startup of Windows works like this, you choose to shutdown your PC, hibernation kicks in and Windows kernel information is written to Hyberfil.sys.  All loaded drivers that are hibernation capable are also notified of shutdown and instructed to prepare for hibernation.  Those conforming drivers are also written to Hyberfil.sys.  Additionally, the hard drive is locked so that nothing can be written to the drive while it is in the hibernation mode.  When you restart your PC the Hyberfil.sys file is read, the stored information is loaded, and Windows springs to life!  All is good.

Now let's say that your machine is in the above situation, you turn on your PC and get a notification that an update is available.  You elect to apply the update.  Now Windows, after having started does not unlock the drive for whatever reason, this will result in a failed update as data cannot be written to protected areas of the disk.

Does this happen a lot?  No, I would say not but if you routinely shutdown your PC with Fast Startup enabled, do not reboot your machine with any frequnecy, and therefore rarely ever have a clean start of your machine I think the chances of you experiencing such failures is greatly increased.

Again, this is an educated guess on my part.