Access Denied message when installing WDS 3.0 beta

Hi csdcomp,

This is a known issue with the beta. The good news is that there is a workaround available. Please use the workaround only if you are comfortable modifying your registry.

Paul Nystrom - MSFT

WORKAROUND

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

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

To work around this issue, follow these steps.

Step 1: Verify that there is a failure to update the registry

a. Open the kb917013.log file. By default, this file is located in the C:\Windows folder. To open the kb917013.log file, click Start, click Run, type %windir%\kb917013.log, and then click OK.

b. On the Edit menu, click Find.

c. In the Find what box, type DoRegistryUpdates failed, and then click Find Next.

d. If a DoRegistryUpdates failed error message is found, a problem exists that is preventing the update of the registry. The error message will be similar to 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 timestamp of each entry.

Step 2: Locate the specific registry key

As soon as you have verified that a registry permission failure has occurred, you must locate the correct registry key to change the permissions and enable Windows Desktop Search 3.0 Beta Engine Preview to install successfully. To do this, follow these steps:

a. 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 (http://support.microsoft.com/kb/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 Desktop Search 3.0 Beta Engine Preview again to capture the registry key.

b. 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.

c. Press CTRL+END to scroll to the end of the Setupapi.log file.

d. On the Edit menu, click Find.

e. 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 be similar to the following example:

#E008 Setting registry value HKCR\MSIDXS

#E033 Error 5: Access is denied.

or

#E008 Setting registry value HKCR\.wll\PersistentHandler

#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 stands for the registry hive that is labeled "HKEY_CLASSES_ROOT." "MSIDXS" or ".wll" is one subkey that is located under that registry hive.

Step 3: 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:

a. Click Start, click Run, type regedit, and then click OK to start Registry Editor.

b. Locate and right-click the registry subkey that you noted in Step 2d, and then click Permissions.

c. Under Group or user names, click Administrators.

d. Under Permissions for Administrators, make sure that the Allow check box for the following entries is selected:? Full Control

? Read

e. Click Apply, and then click OK.

f. On the File menu, click Exit to quit Registry Editor.

The permissions issue for the registry subkey should now be resolved, and Windows Desktop Search 3.0 Beta Engine Preview should install successfully. If you experience additional problems when you try to install Windows Desktop Search 3.0 Beta Engine Preview, repeat these steps as needed.

I was able to find that there was an error writting to the registry, however identifing which key had problems proved unsuccessful. I enabled verbose logging but I was unable to locate an Error: 5 message in the log file. Any suggestions?

The keys I came across were:

HKCR\MSIDXS
HKCR\.gz\PersistentHandler
HKCR\.hqx\PersistentHandler
HKCR\.tar\PersistentHandler
HKCR\.tgz\PersistentHandler
HKCR\.z\PersistentHandler
HKCR\.mdb\PersistentHandler

I try it, but it did not work. I still an not install the search engine.

Boy that was sure fun.

My list was:

.cs
.csv
.mdb
.tif
.tiff
.pps
.rtf

As mentioned before, the keys without the Persistent Handler subfolder, I just set the key itself to allow.

My question to any who know - do I need to reset those keys back to the way they were? Or is it fine to leave them set to Allow?

Yep. Same as mine. I really enjoyed finding these one at a time.

Well, I have done all of the above, and found the registry key affecting mine (after enabling verbose logging). Once I changed permissions on the registry key (HKCR\.wll) I am STILL unable to install this, and still get the exact same failure message. I am the Admin (and only user) of this computer. Anyone have any suggestions? Also, when I check the failure log, I am still getting access denied at the same key I changed permissions for originally, and when I check the registry, the permissions are still what I changed them to....