This article has been archived. It is offered "as is" and will no longer be updated.
When you try to install Windows 2000 from a network share or from a folder location that contains certain hotfix updates that are integrated (slipstreamed) with the Windows 2000 binary files, Setup stops responding (hangs) during the graphical user interface (GUI) portion of Windows Setup.
This issue may occur if one or more of the files that are included in the integrated (slipstreamed) hotfixes are listed in the Drvindex.inf file but are not listed in the Dosnet.inf file.
When Setup detects a hotfix file that has the same name as a file that is listed in the Drvindex.inf file but that is not also listed in the Dosnet.inf file, Setup installs the original Windows file from the cabinet (CAB) files instead of from the i386folder where the integrated hotfix files are located. Because certain files may have dependencies on other hotfix binary files, Setup may stop responding.
To resolve this problem, when you integrate hotfix updates with the operating system source location, follow these steps:
Determine whether any of the files that are inside the hotfix packages are also listed in the Drvindex.inf file that is located in the i386 folder of the operating system installation source location.
If any of the files are listed in the Drvindex.inf file, you must also list those file names in the [SourceDisksFiles] section of the Dosnet.inf file. The Dosnet.inf file is also stored in the i386 folder of the operating system installation source location.
Note When you add files to the [SourceDisksFiles] section of the Dosnet.inf file, you must insert d1, (the letter "d", the number "1", and a comma) in front of the file name. For example, if a hotfix for Ntoskrnl.exe is integrated, you must add the following to the [SourceDisksFiles] section of the Dosnet.inf file:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.