Re: INSTALLING SP2 - GETS THE MESSAGE "Access is denied."

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi!

I tried to set "Deny Write" to the user installing the service pack after I set the 0000FFFF value as Log Level. By doing this I got a much larger SetupAPI.log, but it did not give any answer to the "Access Denied" message.

But I found the reason to my problem in UPDSPAPI.Log and it was the key HKCR\HNetCfg.FwMgr that Administrators was not allowed to do anything with. So now I have got SP2!!!

Morten



"Andrew Morton" <akm@xxxxxxxxxxxxxxxxxxxxxx> wrote in message news:uDwqhbjaHHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
MoF65 wrote:
When I try to install SP2 on one of my 2003 SP1 Server I get the
message "Access is denied." (This is exactly as described in
http://support.microsoft.com/kb/873148).

The SVCPACK.LOG points me to the
ProductInstall.GlobalRegistryChanges.Install section in the
UPDATE.INF file which runs the two sections DelReg=Product.Del.Reg &
AddReg=Product.Add.Reg.

If I try to change the logging level in SETUPAPI.LOG to debug
according to the article http://support.microsoft.com/kb/906485/
(which I have read also applies to Windows Server 2003) it doesn't
work. I have found out that when I start UPDATE.EXE it changes the
LogLevel value from 0000FFFF so I never get the debug info to
SETUPAPI.LOG

How can I get a debug log or else find out which registry that has
the wrong security setting?

I haven't found a solution yet - my computer has the same problem; see thread with subject:
W2003 SP2 won't install - "Access is denied"
dated 16-Mar-2007 in microsoft.public.windowsupdate if you want to read what I've tried so far.

Next I might try changing the permissions on the key containing the LogLevel value to read-only for Administrators, although I suspect that'll make it give up even sooner.

Andrew


.

Quantcast