A Stop: 0xc000026C or Stop: 0xc0000221 "Unable to Load Device Driver" Error Occurs When You Start Windows XP (315241)
The information in this article applies to:
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Professional
This article was previously published under Q315241 SYMPTOMS When you start Windows XP, you may receive one of the
following error messages: STOP: 0xc000026C [Unable to
load device driver] DriverName STOP: 0xc0000221 [Unable to load device
driver] DriverName STOP: 0xc0000221. Bad image check sum, the
image user32.dll is possibly corrupt. The header check sum does not match the
computed check sum. DriverName is the name
of the device driver file. CAUSE This behavior can occur if one of the following conditions
is true:
- A device driver file (.sys) is missing or damaged.
The missing or damaged file is probably the driver file that the
error message mentions. - The User32.dll file may be missing or damaged.
RESOLUTION To resolve this behavior, use the appropriate method for
your symptoms. Missing or Damaged Driver File Use Recovery Console to replace the missing or damaged driver
file. To do so, follow these steps:
- Insert the Windows XP CD-ROM into the CD-ROM or DVD-ROM
drive, and then restart the computer. Select any options that are required to
start the computer from the CD-ROM or DVD-ROM drive if you are prompted to do
so.
- When the "Welcome to Setup" screen appears, press R to
start Recovery Console.
- If your computer is configured for dual booting or multiple
booting, select the relevant Windows XP installation.
- When you are prompted to do so, type the administrator
password, and then press ENTER.
Note In Windows XP Home Edition, the administrator password is\ blank
by default. - At the command prompt, type the following command, and then
press ENTER:
cd windows\system32\drivers
- To rename the damaged driver file, type the following
command, and then press ENTER
ren drivername.sys drivername.bak
where drivername is the name of the
damaged driver file. - To copy the driver from the Windows XP CD-ROM to the
Drivers folder, type the following command, and then press ENTER
copy cd-rom:\i386 drivername where cd-rom is the drive letter for
the drive that contains the Windows XP CD-ROM. - Type exit, press ENTER, and then
restart the computer.
Missing or Damaged User32.dll File Use Recovery Console to replace the corrupted or damaged
User32.dll file, then, if needed, perform an in-place upgrade (also called a
repair install) of Windows XP. To do so follow these steps:
- Insert the Windows XP CD-ROM into the CD-ROM or DVD-ROM
drive, and then restart the computer. Select any options that are required to
start the computer from the CD-ROM or DVD-ROM drive if you are prompted to do
so.
- When the "Welcome to Setup" screen appears, press R to
start Recovery Console.
- If your computer is configured for dual booting or multiple
booting, select the relevant Windows XP installation.
- When you are prompted to do so, type the administrator
password, and then press ENTER.
NOTE: In Windows XP Home Edition, the administrator password is\ blank
by default. - At the command prompt, type the following command, and then
press ENTER:
- To rename the User32.dll file, type the following command,
and then press ENTER:
ren user32.dll user32.bak
- To expand a new copy of the User32.dll file from the
Windows XP CD-ROM to the System32 folder, type the following command, and then
press ENTER:
expand cd-rom:\i386\user32.dl_ c:\windows\system32 where cd-rom is the drive letter for
the drive that contains the Windows XP CD-ROM, and
c:\windows is the drive letter and folder in which
Windows XP is installed. - Type exit, press ENTER, and then
restart the computer.
If Windows XP still fails to start, you may need to perform an
in-place upgrade (also called a repair install) For additional information how to perform an in-place
upgrade of Windows XP, click the article number below to view the article in
the Microsoft Knowledge Base: 315341 How to Perform an In-Place Upgrade of Windows XP
STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 3/29/2004 |
---|
Keywords: | kberrmsg kbprb kbsetup KB315241 |
---|
|