LabMice.net - The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 10, 2003

Install & Setup
  Installation Basics
  Boot Disks
  Boot.ini Files
  Dual Booting
  Hardware Config
  How to Articles
  RIS
  Sysprep
  Unattended Installs
 
Related Links:
  Win2k Install Bugs
  WinNT Upgrade Bugs
  Win9x Upgrade Bugs

 

 

Current Pricing

 

 

 

 

 

 

 

Windows NT to Windows 2000 Upgrade Issues

Although Microsoft supports upgrading Windows NT Workstation and Server to Windows 2000 Professional, you may be better off with a fresh installation. If you absolutely must, you may want to consult this list first. Pay special attention to the Configuration changes made after the Windows 2000 Upgrade is complete. This is by no means a complete list of issues. For an up to date list, check Microsoft Support Online
Newest Issues
Event ID 12 After Installing or Upgrading to Windows 2000
Microsoft Knowledge Base Article: 256222 - When you install or upgrade your computer to Windows 2000, the following Event ID may be logged to the application event log: Event Type: Error Event Source: WINMGMT Event Category: N/A Event ID: 12 Description: Failed to CoGetClassObject for provider "Microsoft|DSLDAPClassProvider|V1.0". Class not registered (0x80040154).

Printer and Ports with Long Names Do Not Appear After Upgrade from Windows NT 4.0 to Windows 2000 
Microsoft Knowledge Base Article: 226193 - Printers with names over 220 characters long do not appear in the Printers folder, but do appear in the registry after upgrading to Windows 2000 from Windows NT 4.0. Printers with names over 259 characters long do not appear in the Printers folder.

Windows 2000 Upgrade Setup Does Not Recognize Qualifying Media CD in First Drive
Microsoft Knowledge Base Article: 285120 - When you are performing a clean Windows 2000 installation by using a Windows 2000 Upgrade CD-ROM on a computer that has two CD-ROM drives, and you are prompted to insert a qualifying media CD-ROM, if you replace the Upgrade disc with the qualifying media disc in the first CD-ROM drive, the following error message may appear: Qualifying operating system was not found.  

When You Try to Upgrade from Windows NT 4.0 to Windows 2000 with Slipstreamed SP1, SP2, or SP3, Cmdlines.txt Does Not Run During the Upgrade
Microsoft Knowledge Base Article 284246 - When you try to upgrade from Microsoft Windows NT 4.0 to Windows 2000 with slipstreamed Service Pack 1 (SP1), Service Pack 2 (SP2), or Service Pack 3 (SP3), the Cmdlines.txt file may not run during the upgrade.

General Issues
After Upgrade to Windows 2000 Last Logged On User Name Displayed
Microsoft Knowledge Base Article: 237890 - After you upgrade your computer running Microsoft Windows NT 4.0 to Windows 2000, the last logged on user name may be visible in the logon dialog box, and this occurs even if you previously configured Windows NT to hide the last logged on user name. 

After Upgrade, Some Programs Do Not Run When You Are Logged In as a Member of the Users Group 
Microsoft Knowledge Base Article: 269259 - After you upgrade from Microsoft Windows NT Workstation 4.0 to Microsoft Windows 2000 Professional, some programs may not function correctly when you are logged in as a member of the Users group. However, the programs do function correctly 

Error Message: Setup Cannot Locate the Windows Installation You Want to Upgrade
Microsoft Knowledge Base Article: 242066 - When you attempt to perform an upgrade from Microsoft Windows NT or an in-place upgrade from within Windows 2000, you may receive the following error message after Setup copies files and restarts the computer: 

Event Log Settings Are Not Retained During Windows 2000 Upgrade
Microsoft KB Article Q227340. When you upgrade a computer from Microsoft Windows NT 4.0 to Windows 2000, your custom settings for the Event Log tool are not retained. These settings are instead reset to the default values. 

Group Descriptions Not Updated to Windows 2000 Equivalent Following Upgrade
Microsoft KB Article Q220961 The built-in group descriptions from prior versions of Windows NT are not changed to that of Windows 2000 default descriptions following an upgrade. (updated 12/29/99)

Files in NETLOGON Share Moved During Windows 2000 Upgrade 
Microsoft Knowledge Base Article: 229679 - In Microsoft Windows NT versions 3.x and 4.0, domain controllers maintain a NETLOGON share in which administrators typically keep logon scripts and system policy files. After a computer is upgraded to Windows 2000 and promoted to a domain controller, the NETLOGON share and its contents are moved to a new location known as SYSVOL that is part of an automatically replicated folder structure that is replicated amongst domain controllers in the same domain. 

How to Prevent Windows 2000 Upgrade from Modifying Custom Security
Microsoft Knowledge Base Article: 260242 - The Windows 2000 upgrade process applies Windows 2000 default security settings to registry keys and file system objects. This process overwrites any custom permissions that you previously defined. 

Installation Options Ignored After Selecting Any Accessibility Options in Winnt32.exe
Microsoft Knowledge Base Article: 222963 - When you run Winnt32.exe to upgrade your operating system to Windows 2000 and you select any accessibility options, the options to choose your installation folder and installation partition are ignored. Setup defaults to using the Winnt folder on the primary partition. 

Issues with Removing Windows 2000 and Reinstalling Windows NT 4.0
Microsoft Knowledge Base Article: 257754 - Removing Windows 2000 and installing Microsoft Windows NT 4.0 is a manual process; there is no uninstall process available. This article describes preventative steps that you should take to preserve data before you attempt to remove Windows NT 

NMAgent Takes Over CPU Processing When IPCONFIG /RELEASE Is Performed 
Microsoft Knowledge Base Article: 225813 - After you upgrade from Microsoft Windows NT 4.0 to Windows 2000, using the "IPCONFIG /RELEASE" command may halt processing on the computer. When this occurs, CPU usage may reach 90 to 100 percent. (

Running Windows 2000 Setup from Floppy Disks or CD-ROM Does Not Upgrade Windows NT4.0 or Windows 98
Microsoft Knowledge Base Article: 225774 - When you boot your Microsoft Windows NT 4.0-based or Microsoft Windows 98-based computer from the Windows 2000 CD-ROM or floppy disks to run Windows 2000 Setup, you receive the following message:

Saving and Restoring Existing Windows NT Shares
Microsoft Knowledge Base Article: 125996 - If you need to: reinstall Windows NT over an existing installation (a clean install, not an upgrade), move all of your data drives from one server to another, install Windows NT to another directory or drive on a computer that already has Windows NT installed you can save the share names that exist on the original Windows NT installation, including any permissions assigned to those shares.

Upgrading to Windows 2000 Upgrades Existing Novell Client
Microsoft Knowledge Base Article: 218158 - Windows 2000 Setup upgrades all Intel-based (x86) computers running version 4.7 or earlier of a Novell client to version 4.51. 

Winnt32.exe Forces Restart Even When Other Programs Are Open with Unsaved Data
Microsoft Knowledge Base Article: 222958 - When you run Winnt32.exe to upgrade Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows NT to Windows 2000, you receive the following prompt if other programs are running with unsaved data: Save Document? If you click Cancel, the computer is restarted and you have no opportunity to save the data. 

Windows 2000 Cannot Upgrade over BackOffice 4.5
Microsoft Knowledge Base Article: 253872 - When you attempt to install Windows 2000 by using the Windows 2000 upgrade CD-ROM, Setup prompts you for the CD-ROM of a previous version of Windows NT to confirm that you are upgrading. However, the Windows 2000 compliance checking feature feature does not recognize the BackOffice 4.5, Chinese Windows NT 4.0 Workstation, or Korean Windows NT 4.0 Workstation CD-ROM as valid media. 

Windows 2000 Setup Upgrades Existing NTFS File System Volumes
Microsoft Knowledge Base Article: 198904 - When you install Windows 2000, existing NTFS volumes are upgraded to a newer version of the NTFS file system. This newer version of the NTFS file system includes capabilities such as disk quotas, encrypted files, journaling, and a number of other features that Windows 2000 components rely on to function correctly. 

Windows NT 4.0 Cannot Access Windows 2000 FAT32 Partition
Microsoft Knowledge Base Article: 214404 - If you install Windows 2000 on a partition using the FAT32 file system on a computer that also has Windows NT 4.0 installed, the Windows NT 4.0 installation cannot gain access to the FAT32 partition. 

Windows NT 4.0 Files Remain After Windows 2000 Upgrade
Microsoft Knowledge Base Article: 219023 - After you upgrade from Microsoft Windows NT 4.0 to Windows 2000, the following files may remain: 

Winnt32.exe Forces Restart Even When Other Programs Are Open with Unsaved Data
Microsoft Knowledge Base Article: 222958 - When you run Winnt32.exe to upgrade Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows NT to Windows 2000, you receive the following prompt if other programs are running with unsaved data: Save Document? If you click Cancel, the computer is restarted and you have no opportunity to save the data. 

Configuration Issues

Cannot Connect to AOL After Upgrading to Windows 2000
Microsoft Knowledge Base Article: 228086 - When you attempt to connect to America Online (AOL) after upgrading to Windows 2000, you may receive one of the following error messages in AOL: 

Cannot Find Active Directory Domain Controller When Upgrading Windows NT 4.0 PDC
Microsoft Knowledge Base Article: 244030 - After you upgrade a Windows NT 4.0-based primary domain controller (PDC) to Windows 2000, Dcpromo.exe runs but configures the server as a member server. Dcpromo.exe does not default to a domain controller promotion. 

Cannot Create Partition Greater than 1 GB
Microsoft KB Article Q137474 When you attempt to install Windows NT on a computer with some SCSI controllers, using two or more drives containing free space, Windows NT does not allow creation of partition sizes larger than 1 gigabyte (GB). 

Cannot Print After Upgrading from Windows NT 4.0 to Windows 2000
Microsoft KB Article Q233546 After you upgrade from Microsoft Windows NT 4.0 to Windows 2000, you may not be able to print.

Cannot Log On to Windows 2000 After You Upgrade from Windows NT 3.51
Microsoft KB Article Q243997 You cannot log on a computer running Windows 2000 after you upgrade it from Windows NT 3.51. You receive an error message: 

Computer Name Does Not Match the Windows 2000 Domain Name After Upgrade
Microsoft Knowledge Base Article: 262376 - The fully qualified domain name computer name does not match the Windows 2000 domain name because a Microsoft Windows NT 4.0 upgrade automatically clears the.. 

Dial-Up Connection Status Shows Less Details After Upgrade
Microsoft Knowledge Base Article: 227336 - When you view the Dial-Up Networking Connection Status dialog box after upgrading your Microsoft Windows NT-based computer to Windows 2000, the following information from the Dial-Up Networking Monitor tool is no longer displayed: The number of frames in and out; The percentage of compression in and out; The following device errors: CRC, timeouts, alignment, framing, hardware overruns, and buffer overruns. This issue occurs because that information is now available in the Rasmon tool.

Error Message: Windows 2000 Is Installed on a Drive Formatted with the OS/2 File System (HPFS)
Microsoft Knowledge Base Article: 270070 - When you upgrade a system running Windows NT 4.0 Terminal Server to Windows 2000, you may receive the following error message after you enter the alphanumeric product key: Windows 2000 is installed on a drive formatted with the OS/2 File System (HPFS). Windows 2000 does not support this file system. You must convert this drive to the Windows 2000 File System (NTFS) before upgrading. This error message occurs even though you do not have any (unsupported) HPFS volumes on the system. 

Power Options Tool in Control Panel Renamed to UPS After Upgrade
Microsoft KB Article Q219024 After you upgrade from Microsoft Windows NT 4.0 to Windows 2000, the Power Options tool in Control Panel may be renamed to UPS. 

SAP Agent Uninstalled After You Upgrade to Windows 2000
Microsoft Knowledge Base Article: 210817 - After you upgrade your Microsoft Windows NT-based computer to Windows 2000, the SAP Agent service is no longer installed. Note that this occurs even if you previously installed and used the SAP Agent before upgrading to Windows 2000. 

Start Menu Icons Are Missing After Upgrade from Windows NT 3.51
Microsoft KB Article Q227625 After you upgrade from Microsoft Windows NT 3.51 to Windows 2000, the shortcuts that are created in place of the Windows NT 3.51 Program Manager group items may not display icons correctly. 

Task Scheduler Service Starts Automatically After Upgrade
Microsoft KB Article Q234632 After you upgrade your Microsoft Windows NT 4.0-based computer to Windows 2000, the Task Scheduler service starts automatically, and this occurs even if you previously disabled this feature. 

Upgrading Windows NT 4.0 Changes Boot.ini to the Default Time-Out Value
Microsoft KB Article Q226043 When you upgrade to Windows 2000 from Microsoft Windows NT Server 4.0, the time-out value in the Boot.ini file reverts to the default value of 30 seconds. 

Using User Profiles with Both Windows 2000 and Windows NT 4.0
Microsoft KB Article Q224012 Users with roaming user profiles can log on interchangeably to computers running Windows NT 4.0 and Windows 2000. Both operating systems can read the same user profile and do not prevent users from logging on from either operating system.

Windows 2000 DHCP Server Continues to Assign Addresses After Upgrade
Microsoft Knowledge Base Article: 225148 - After you upgrade a Microsoft Windows NT 4.0 server to Windows 2000, Dynamic Host Configuration Protocol (DHCP) continues to assign addresses, even though it is not authorized to do so. 

Hardware and Driver Issues
Accel Graphics Eclipse Video Adapter Is Not Detected in Windows 2000
Microsoft Knowledge Base Article: 227236 - When you upgrade your Microsoft Windows NT 4.0-based computer to Windows 2000, your Accel Graphics Eclipse or AccelPro video adapter is not detected properly.

Advanced Video Adapter Configuration Settings May Be Missing After You Upgrade to Windows 2000
Microsoft Knowledge Base Article: 228286 - After you upgrade your Microsoft Windows NT 4.0-based computer to Windows 2000, Control Panel extensions for your video adapter are no longer available. 

Device Manager Lists Both VGA and Cirrus Logic Adapters After Upgrading from Windows NT4.0
Microsoft KB Article Q227224 After you upgrade from Microsoft Windows NT 4.0 to Windows 2000 on a computer with a Cirrus Logic video adapter using the Cl54xx.sys driver, both a Cirrus Logic and a VGA video adapter are listed in Device Manager. 

Display Is Limited to 16 Colors After Upgrading to Windows 2000
Microsoft Knowledge Base Article: 268467 - After you install Windows 2000, your display may be limited to 16 colors and 640 X 480 resolution. In addition, the properties of Display adapter in Device Manager will have a yellow exclamation mark (!) and a Code 10 with the following status: The device cannot start. (Code 10). This may occur if you have a display adapter that uses the NVIDIA chip set and the basic input/output system (BIOS) on your computer does not have an interrupt request (IRQ) assigned for the display adapter. 

Drive Letters Assigned to Unsupported Partition Types
Microsoft Knowledge Base Article: 221799 - After you upgrade to Windows 2000, drive letters may be assigned to partitions that previously did not have drive letters. When you try to gain access to one of the partitions, you may receive the following error message: The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted. When you view the Logical Disk Manager (LDM) snap-in, the partition has a status of "healthy" but does not have a file system type. 

Incompatible Windows NT4.0 Print Drivers Are Blocked and Replaced When Upgrading
Microsoft KB Article Q224966 When you upgrade from Microsoft Windows NT 4.0 to Windows 2000, incompatible Windows NT 4.0 printer drivers (such as the Okidata Okipage 20 driver) are blocked and replaced with the driver included with Windows 2000.

Matrox PowerDesk Tools Unavailable after Windows 2000 Upgrade 
Microsoft Knowledge Base Article: 227476 - After you upgrade your Microsoft Windows NT-based computer using a Matrox video adapter to Windows 2000, the Matrox QuickDesk and PowerDesk utilities no longer function properly. 

Mouse May Not Work After Installing Windows 2000
Microsoft Knowledge Base Article: 214632 - After you install Windows 2000, or upgrade from Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows NT 4.0, your bus or InPort mouse does not work. 

NEC Card Wizard Does Not Work After Windows 2000 Upgrade
Microsoft KB Article Q226031 After you upgrade from Microsoft Windows NT 4.0 to Windows 2000, the NEC Card Wizard program may no longer function. When you run the program, it may immediately stop responding (hang). 

Network Adapter Settings Are Lost After Upgrading to Windows 2000
Microsoft Knowledge Base Article: 224011 - When you upgrade a computer participating on a network to Windows 2000, static configuration settings such as the Internet Protocol (IP), Domain Name Service (DNS) server, Microsoft Windows Internet Naming Service (WINS), and default gateway address may be lost and may be set to obtain addresses automatically using Dynamic Host Configuration Protocol (DHCP).

Parallel Port Devices Do Not Work After You Upgrade from Windows NT 4.0
Microsoft Knowledge Base Article: 265409 - After you upgrade from Windows NT 4.0 to Windows 2000, parallel port (LPT) devices may not be detected. The port appears in Device Manager as "Parallel output only" or ECP 1.x with an exclamation mark in a yellow circle. 

Some SCSI Adapter Drivers Previously Included in Windows NT 4.0 Are Unavailable in Windows 2000
Microsoft KB Article Q228104 There are several Small Computer System Interface (SCSI) adapter drivers that have been removed from Windows 2000 that were previously included in Microsoft Windows NT 4.0 and 3.51.

Uninterruptible Power Supply Goes into Battery Mode During Windows 2000 Installation
Microsoft KB Article Q238860 When you install Windows 2000 on a computer that has an uninterruptible power supply (UPS) attached, the computer may go into Battery mode. 

Windows 2000 Does Not Detect Stbv128m.sys After Upgrade from Windows NT 4.0
Microsoft KB Article Q227215 When you upgrade a Microsoft Windows NT 4.0-based computer that is running the Stbv128m.sys driver to Windows 2000, your monitor is not detected in Device Manager in Windows 2000. 

Windows Hangs at "Loading Machine Info" with HighPoint UltraDMA ATA/66 Controller
Microsoft Knowledge Base Article: 243018 - If you start your computer using a Windows 2000 CD-ROM to install Windows and you have installed a HighPoint UltraDMA ATA/66 hard disk controller, the computer may stop responding (hang) while the following information is displayed:
Loading Machine Information. You cannot press F6 to install a secondary controller driver. If you upgrade from Windows NT 4.0 or Windows 95/98, you may receive the following error message: Stop 0x0000007b INACCESSIBLE_BOOT_DEVICE  

3rd Party Software Issues
Blue Screen on Reboot After Installing Corel CD Creator 2.0 
Microsoft KB Article Q154915 When you restart your computer after installing Corel CD Creator version 2.0, you may receive one of the following error messages on a blue screen: 

Error Message: Microsoft Windows 2000 Has Detected Software That Is Not Completely Installed on Your Computer
Microsoft Knowledge Base Article: 242435 - When you attempt to upgrade to Windows 2000, you may receive the following error message: Microsoft Windows 2000 has detected software that is not completely installed on your computer. Windows 2000 Setup cannot continue until you finish installing this software. To finish the installation process for this software quit Windows 2000 Setup. Log off of your computer and then log back on again. Restart Windows 2000 Setup. The error message occurs again even after you log off and back on as the error message suggests. 

Windows 2000 May Stop Responding When You Attempt to Run Adaptec's Easy CD Creator
Microsoft KB Article Q237468 Windows 2000 may stop responding (hang) at the splash screen or may not start properly when you attempt to run Adaptec's Easy CD Creator versions 3.5b or earlier. 

Other Issues
Cannot Alter Down-Level Domain Name During Upgrade from Windows NT 4.0 to Windows 2000 
Microsoft Knowledge Base Article: 240156 - You cannot change the NetBIOS domain name when you are upgrading a Microsoft Windows NT 4.0-based primary domain controller to Windows 2000. You can specify the Domain Name System (DNS) domain name, but you cannot alter the automatically created down-level NetBIOS domain name. You can change this name only after the upgrade and Dcpromo.exe processes have finished, by demoting and repromoting the server 

Computer Name Does Not Match the Windows 2000 Domain Name After Upgrade
Microsoft Knowledge Base Article: 262376 - The fully qualified domain name computer name does not match the Windows 2000 domain name because a Microsoft Windows NT 4.0 upgrade automatically clears the Change primary DNS suffix when domain membership changes check box. After the domain controller promotion process (Dcpromo.exe) is run on a domain controller, you are unable to change the computer name. 

Default Tree and Context Settings Missing After Upgrading to Windows 2000
Microsoft Knowledge Base Article: 222024 - After you upgrade a Microsoft Windows NT 4.0 primary domain controller (PDC) running Gateway Services for NetWare (GSNW) Windows 2000 Server, the default tree and context settings may be missing. 

Err Msg: Line <nnnn> of the Inf Is Corrupt or Invalid...
Microsoft Knowledge Base Article: 210888 - During an unattended upgrade from Microsoft Windows NT 4.0 to Windows 2000, you may receive the following error message: Line nnnn of the Inf is corrupt or invalid. Setup cannot continue. where nnnn is the number of the damaged or invalid line. 

NMAgent Takes Over CPU Processing When IPCONFIG /RELEASE Is Performed
Microsoft KB Article Q225813 After you upgrade from Microsoft Windows NT 4.0 to Windows 2000, using the "IPCONFIG /RELEASE" command may halt processing on the computer. When this occurs, CPU usage may reach 90 to 100 percent. 

SendPort DNS Registry Key Does Not Work as Expected
Microsoft Knowledge Base Article: 260186 - When you upgrade your Microsoft Windows NT 4.0-based computer that is running Domain Name Service (DNS) to Windows 2000, you may experience name resolution issues. 

Unattended Setup May Not Work During Upgrade from Windows NT 4.0 To Windows 2000
Microsoft Knowledge Base Article: 257814 - You may receive the following error message when you automate the upgrade of a Windows NT 4.0-based computer to Windows 2000:(updated 4/13/2000)

Windows NT 4.0 Disk Administrator Not Compatible with Windows 2000 
Microsoft KB Article Q246032 If you use the Disk Administrator tool (Windisk.exe) from Microsoft Windows NT 4.0 in Windows 2000, the master boot record (MBR) on your hard disk may be overwritten. 

Windows NT 4.0 Files Remain After Windows 2000 Upgrade
Microsoft KB Article Q219023 After you upgrade from Microsoft Windows NT 4.0 to Windows 2000, the following files may remain: 

 

Entire contents
© 1999-2003 LabMice.net and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by LabMice.net. Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with LabMice.net. The products referenced in this site are provided by parties other than LabMice.net. LabMice.net makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.