June 26

Windows: Installing Windows Server 2003 Service Pack – Access is denied error

You receive an error message when you try to install Windows XP Service Pack 2 or Windows Server 2003 Service Pack 1: “Access is denied”
Article ID: 873148 – View products that this article applies to.
Notice
This article is intended for advanced computer users.

SYMPTOMS
When you try to install Windows XP Service Pack 2 (SP2) or Windows Server 2003 Service Pack 1 (SP1), you may experience any one of the following issues:

You cannot install the service pack.
You receive the following error message:
Service Pack setup has failed. Access is denied
The Svcpack.log file contains the following error message:
DoRegistryUpdates failed

CAUSE
These issues may occur when permissions for one or more registry keys are restricted in a way that prevents the update of those registry keys. A failure to update a registry key may cause the Setup program to fail. To verify that there is a failure to update the registry, see the “More Information” section.

WORKAROUND
Advanced users
These methods are intended for advanced computer users.

Method 1: Locate the registry key and reset the registry permissions
After you follow these steps, reinstall the service pack. You may have to follow these steps multiple times to resolve the issue.

Note You must be a member of the Administrators security group to complete these steps.

Step 1: Locate the specific registry key
To locate the correct registry key to change the permissions and enable Windows XP SP2 or Windows Server 2003 SP1 to install successfully, follow these steps:

Include registry information in the Setupapi.log file by enabling verbose logging. For more information about how to enable verbose logging, click the following article number to view the article in the Microsoft Knowledge Base:
906485 How to enable verbose logging on a Windows XP-based computer
Note By default, registry keys are not recorded in the Setupapi.log file.

After you enable verbose logging, install Windows XP SP2 or Windows Server 2003 SP1 again to capture the registry key.
Open the Setupapi.log file. By default, this file is located in the C:Windows folder. To open the Setupapi.log file, click Start, click Run, type %windir%setupapi.log, and then click OK.
Press CTRL+END to scroll to the end of the Setupapi.log file.
On the Edit menu, click Find.
In the Find what box, type Error 5: Access is denied under Direction, click Up, and then click Find Next.

The found entry in the Setupapi.log file should resemble the following example:
#-007 Deleting registry key HKCRvnd.ms.radio
#E033 Error 5: Access is denied.
Note The line before the “Access is denied” entry indicates the registry key in question. In this case, HKCR represents the registry hive that is labeled “HKEY_CLASSES_ROOT.” “vnd.ms.radio” is one subkey that is located under that registry hive.

Step 2: Reset the registry permissions
As soon as you have found the registry subkey that has the incorrect permissions, update the permissions for that subkey.

To update the permissions of the registry subkey, follow these steps:

Click Start, click Run, type regedit, and then click OK to start Registry Editor.
Locate and right-click the registry subkey that you noted in Step 2d, and then click Permissions.
Under Group or user names, click Administrators.
Under Permissions for Administrators, make sure that the Allow check box for the following entries is selected:
Full Control
Read
Click Apply, and then click OK.
On the File menu, click Exit to exit Registry Editor.

The permissions issue for the registry subkey should now be resolved, and Windows XP SP2 or Windows Server 2003 SP1 should install successfully. If you experience additional problems when you try to install Windows XP SP2 or Windows Server 2003 SP1, repeat these steps as needed.

Method 2: Reset your operating system back to the default settings
To reset your operating system back to original installation default security settings, follow these steps:

Click Start, click Run, type cmd, and then press ENTER.
Type secedit /configure /cfg %windir%repairsecsetup.inf /db secsetup.sdb /verbose, and then press ENTER.

You receive a “Task is completed” message, and a warning message that something could not be done. You can safely ignore this message. For more information about this message, view the %windir%SecurityLogsScesrv.log file.

For more information about how to reset security settings back to the defaults, click the following article number to view the article in the Microsoft Knowledge Base:
313222 How to reset security settings back to the defaults

MORE INFORMATION
To verify that there is a failure to update the registry, follow these steps:

Open the Svcpack.log file. By default, this file is located in the C:Windows folder. To open the Svcpack.log file, click Start, click Run, type %windir%svcpack.log, and then click OK.
On the Edit menu, click Find.
In the Find what box, type DoRegistryUpdates failed, and then click Find Next.
If a DoRegistryUpdates failed error message is found, a problem exists that is preventing the update of the registry. The error message will resemble the following example:
xxxx.xxx: DoInstallation:DoRegistryUpdates failed.
xxxx.xxx: Access is denied.
xxxx.xxx: Message displayed to the user: Access is denied.
Note xxxx.xxx represents the time stamp of each entry.

Similar problems and solutions
If you are still experiencing the problem in this article, you may have a similar but different problem. For more information about a similar problem and resolution, click the following article number to view the article in the Microsoft Knowledge Base:
828213 “Access is denied” error message when you try to install Windows XP Service Pack 1
If these articles do not help you resolve the problem, or if you experience symptoms that differ from those that are described in this article, search the Microsoft Knowledge Base for more information. To search the Microsoft Knowledge Base, visit the following Microsoft Web site:
http://support.microsoft.com
Then, type the text of the error message that you receive. Or, type a description of the problem in the Search Support (KB) field.

Article ID: 873148 – Last Review: November 27, 2007 – Revision: 6.3

APPLIES TO
Microsoft Windows XP Service Pack 2, when used with:
Microsoft Windows XP Home Edition
Microsoft Windows XP Professional
Microsoft Windows Server 2003 Service Pack 1, when used with:
Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
Microsoft Windows Server 2003, Web Edition
Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
Microsoft Windows Server 2003, Standard x64 Edition
Microsoft Windows Server 2003, Datacenter x64 Edition
Microsoft Windows Server 2003, Enterprise x64 Edition

By: Microsoft®


Copyright 2021. All rights reserved.

Posted June 26, 2013 by Timothy Conrad in category "Windows

About the Author

If I were to describe myself with one word it would be, creative. I am interested in almost everything which keeps me rather busy. Here you will find some of my technical musings. Securely email me using - PGP: 4CB8 91EB 0C0A A530 3BE9 6D76 B076 96F1 6135 0A1B