Specifying Additional Upgrade Packs When Upgrading from Windows 95/98 to Windows 2000

This article was previously published under Q231418
This article has been archived. It is offered "as is" and will no longer be updated.
When you upgrade from Microsoft Windows 95 or Microsoft Windows 98 to Windows 2000, upgrade packs (also known as migration DLLs) are required because of registry and program differences between the operating systems. When you start the upgrade process, you are prompted for additional upgrade packs to those included on the Windows 2000 CD-ROM. Currently, Setup (Winnt32.exe) checks the following locations for upgrade packs:
  • User-specified location
  • The I386\Win9xmig folder on the Windows 2000 CD-ROM

User-Specified Location

You can specify a network location or a local source for upgrade packs. When the location is specified, it and all subfolders are scanned for any files named Migrate.dll. These files are then processed to determine if they are required for the upgrade. If so, the files are then copied to the following location:
This copies the Migrate.dll files and any files required by the DLLs. The folder structure of the source also remains intact. The Dllnnnnnn folder is created by Setup with a unique name (such as Dll00013).

The Windows 2000 CD-ROM

Setup copies migration DLLs from the I386\Win9xmig folder on the CD-ROM that are needed during the upgrade process to the location noted above. Using this method, an administrator can create a distribution share that contains additional vendor-supplied migration DLLs.

Using an Unattended Answer File

The location of migration DLLs can also be specified in an unattended answer file in the [Win9xUpg] section as follows:
MigrationDlls = path to migration DLL, path to migration DLL
NOTE: The path should refer only to the folder containing the DLL, not the actual DLL file name.

Article ID: 231418 - Last Review: 10/21/2013 22:08:58 - Revision: 3.1

Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbinfo kbsetup KB231418
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)