Service Pack 2 could not backup registry key (still having a probl

From: John (John_at_discussions.microsoft.com)
Date: 08/29/04


Date: Sun, 29 Aug 2004 06:03:03 -0700

I attempted to change the security through regedit and it won't allow me due
to insufficient permissions. I even tried via safe mode.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

John wrote:

> I am trying to apply service pack 2 to an XP Home edition OS. I am getting
> the following error for multiple registry keys so I have to abort the install.
>
> Service Pack 2 could not backup registry key Access denied.
>
> Any ideas?
Hi

You can trace which registry key is causing the trouble using the
setupapi.log in the windows folder (this log file is updated during
a service pack installation).

Here is a previous post about this:

From: <stephensrob1@hotmail.com>
Subject: XP SP2 "Access Denied" & the Fix
Date: Sat, 14 Aug 2004 08:22:57 -0700
Newsgroups: microsoft.public.windowsxp.general

<quote>
As with SP2 RC2, I am having the same problem with the GA
release of SP2. "Access Denied" during installation.
This is error can be worked around by reading the
setupapi.log under the windows directory. I am
posting this to see if others are having the problem. For
some reason several registry keys related to windows media
player and a few others do not have any permissions set
for admin and system.

Specifically the following need to have permissions set to
full control for admin & system:

HKCR/vnd.ms.radio
IP6FwAPI.NetFirewallV6Manager
HKCR/WMPlater.OCX/EditFlags
HKCR/Software/Classes/UICTL* may vary
HKCR/Software/Classes/ADDC* may vary

you may have others so check the log for "Unable to delete
registry , Access Denied"

You may need to go thru the install a few times, as you
may fix one set, the next time you run it you may
encounter a new set. The best thing to do is check the
first 3 listed above and the set full control on
permission to HKCR/Software/Classes and its child objects
for Admin and System only.
</quote>

The above might be a very laborious if there are several registry
keys that have a permission issue. In that case, it would be
better to reset the security settings back to the defaults for
all registry keys.

More here on how to do that:

How To Reset Security Settings Back to the Defaults
http://support.microsoft.com/?kbid=313222

If you only want to reset the registry permissions,
add this to the secedit command line:

   /areas REGKEYS

-- 
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scriptcenter/default.mspx
 
 
 
Expand AllCollapse All 


Relevant Pages

  • Re: What is .Net?
    ... You have a policy and you have permissions. ... C: drive and start if from there: reason: not enough security rights. ... how the hell can you configure the .NET framework ... are doing and that this software can be trusted, or else you won't install ...
    (microsoft.public.dotnet.general)
  • Reinstalling WMP
    ... I don't know what the permissions were reset to. ... I tightened up the security on it and figured I'll ... reinstall by editing the .inf files that came with the WMP install package. ... Change the line to the new folder. ...
    (microsoft.public.security)
  • Re: Still Read-only
    ... or after an install of XP or W2k3 will make things ... That is how XP and W2k3 are. ... and file permissions are different things. ... Security) ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Default Regitry Permissions
    ... install is probably irrelevant. ... and the Administrators group "Special Permissions - Full Controll" ... As far as I can tell, it's not a local security policy. ... I've confirmed these settings by running "Resultant Set of Policy on ...
    (microsoft.public.windows.server.security)
  • Re: permissions in widows xp home edition
    ... This would be done by the admin just ... >>after the install, and it grants the Users group change ... >>the tightened security of W2k and now XP, ... >>> edition is not the easiest to use for permissions. ...
    (microsoft.public.windowsxp.security_admin)