This happened with my main computer, the one I work everyday, that full with different programs. I have noticed long before that something wrong with the registry. When I installed iSpring (a software to convert ppt to swf), it always failed to register the .dll with errors that meant “Access is denied”, like this :
With this error, the iSpring failed to come out in my Power Point 2007 – so I couldn’t use it.
After had good experience with my other computer, this morning I wanted to install the Windows Service Pack3 in this one. First time, it failed with “Service Pack 3 setup error. Access is denied”.
My first step to solve is uninstall the AntiVirus (Symantec End Point), restart, then run again the SP3 installation. Again it failed with the same error.
I did google and found this Microsoft support webpage. I followed the Advance Troubleshooting as below (I copied from that webpage):
- Download and install Subinacl.exe file. Follow this Microsoft Website
- Start Notepad
- Copy and paste the following text into Notepad :
cd /d “%ProgramFiles%\Windows Resource Kits\Tools”
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f /grant=system=f
subinacl /subdirectories %windir%\*.* /grant=administrators=f /grant=system=f
secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose - Save this Notepad file as Reset.cmd
- Double-click the Reset.cmd to run the script.
After restart, the Microsoft ISA Client software didn’t work. I just uninstall it. Then I run XP SP3 installation, voila!! it went through smoothly. Afterward, I reinstall the Microsoft ISA Client and also the Symantec End Point.
Finally, I reinstall the iSpring. This time it went through also smoothly and it came out in the Power Point 2007.
My conclusion is, there was really a problem with authorization in the Registry and it was solved by “Reset the registry and file permissions” using reset.cmd.
