Microsoft Knowledge Base Email Alertz

(918608) - Explains that the New Hardware Found wizard may start when you start a computer that is running the .NET Framework 2.0.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 918608 - Last Review: December 3, 2007 - Revision: 1.2

The New Hardware Found wizard may start and try to install the .NET Runtime Optimization Service when you start a computer that is running the .NET Framework 2.0

SYMPTOMS

When you start a computer that is running the Microsoft .NET Framework 2.0, the New Hardware Found wizard may start. This wizard may try to install the .NET Runtime Optimization Service V2.0.Number_Number.

CAUSE

This issue occurs because a race condition may exist when the computer creates legacy device instances for a Win32 service or for a legacy kernel driver. When the computer creates a legacy device instance, the following registry subkey is created:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_<ServiceName>\0000
The device instance key has a legacy registry value. This value identifies a legacy device that should not be installed. Additionally, the value of the legacy registry subkey is set just after the key is created. When the key is created and the value for the key is not set, a re-enumeration of the device tree may be initiated. In this re-enumeration, the value of the key does not yet exist. Therefore, the key is perceived not to reference a legacy device. When this race condition occurs, a Win32 service may be installed as a device instead of a service.

RESOLUTION

To resolve this issue, examine the device manager to see whether the .NET Runtime Optimization Service V2.0.Number_Number is installed as a device. If the service is installed as a device, you must uninstall the device. Then, run the following command to install the service correctly:
mscorsvw.exe -i
To do this, follow these steps:
  1. Click Start, click Run, type DEVMGMT.MSC, and then click OK.
  2. Right-click .NET Runtime Optimization Service V2.0.Number_Number if the device appears, and then click Uninstall.
  3. In the Confirm Device Removal dialog box, click OK.
  4. At the command prompt, run the following command:
    %WINDIR%\Microsoft.NET\Framework<64>\v2.0.Number\mscorsvw.exe -i
    Note If the service is already installed correctly, you may receive the following error message:
    Failed to install Microsoft .NET Runtime Optimization Service.
    You can ignore the error message.

APPLIES TO
  • Microsoft .NET Framework 2.0
Keywords: 
kbinfo kbtshoot kbprb KB918608
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate