If you experience the 80070005, 80070490, 80080008, and 643 errors a reformat and reinstall is probably faster than going through the following steps. Perform a backup of data, license keys, and settings then execute a reformat of the hard drive and reinstall of the operating system. Occasionally you can do an in-place upgrade of the operating system if your OEM disk matches the service pack installed on the target machine.
For those of you who wish to spend an inordinate amount of time fixing the 80070005, 80070490, and 643 errors rather than doing a repair install of Vista, read on. As an IT guy, I wanted to go through the process of fixing the errors in case a repair or in-place upgrade did not work. The in-place upgrade solution will not work if you attempt to use an OEM disk that does not include the current service pack installed on the target computer. Often, even if you remove the service pack on the target machine, the in-place upgrade does not work.
Part One
Go to Aaron Stebner’s Weblog, download the SubInACL repair tool. In my case, I installed the tool to the windows\system32 folder rather than the default Aaron mentions.
Make a batch file that contains the following.
@echo off
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=system=f
@Echo =========================
@Echo Finished.
@Echo =========================
@pause
Run the batch file as an administrator (right-click, run as administrator)
Reboot
Part Two
Download and install the system readiness tool for Vista
Reboot
Part three
Download and run the latest windows update software. See this site for more information.
What causes the errors in the first place?
ReplyDeleteIn the three cases I've experienced the issue, two were viruses one was an interruption in a service pack update. I've only been successful at using the methods once. A 30% success rate may show that the repair methods aren't worth the time.
ReplyDelete