Signed Drivers May Appear as Unsigned During Setup

View products that this article applies to.

This article was previously published under Q282755

Expand all | Collapse all

SYMPTOMS

During the Text-mode portion of Setup, if you press F6 to install a third-party driver, the driver files are copied, but Setup may act as if the driver is unsigned during the GUI-mode portion of Setup even if the driver is signed.

Back to the top

CAUSE

This behavior can occur if press F6 to install third-party mass-storage driver at the start of the Text-mode portion of Setup. The Text-mode portion of Setup copies the Oemsetup.inf, .cat, and .sys files to the Windows\Oemdir folder. However, legacy code is still being called; this code copies the Oemsetup.inf file to the Windows\Inf folder and scoem01.inf, etc. When Plug and Play processes the files during the GUI-mode portion of Setup, it cannot tell which .inf file to trust.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 (http://support.microsoft.com/kb/260910/EN-US/ ) How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

   Date        Time    Version        Size     File name
   -------------------------------------------------------
   09/19/2000  05:54p  5.0.2195.2305  380,048  Setupdd.sys

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

Back to the top

MORE INFORMATION

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 (http://support.microsoft.com/kb/249149/EN-US/ ) Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Back to the top