Code 41 Message

[Kristin]

My DVD-ROM & CD-R/RW suddenly stopped reading disks. They
open and close, but the system doesn't seem to read them.
The device manager has yellow "!" sign by each drive and
says,"Windows successfully loaded the device driver for
this hardware but cannot find the hardware device. (Code
41)". Does anyone know what this means or how to fix it???
Please help me!!

 

[Jason Tsang]

Goto http://aumha.org/win5/a/xpcd.php#problems
See the second "problem" (read the caveats)
Run the provided registry patch

That should fix your problem (basically, a filter driver is missing or
non-operational, the registry patch will delete the filter drivers
references for your cdrom(s))


Basically, the reg file from above carries out the steps displayed at this
website


CD-ROM Drive or DVD-ROM Drive Missing After You Install Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;320553

CD-ROM Access Is Missing and Messages Cite Error Code 31, Code 32, Code 19,
or Code 39 After You Remove Easy CD Creator in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314060


[note this also fixes code 41 errors too as mentioned in the last kb article
listed]

 

[Scott]

Had the same prob when I uninstalled Clone-cd. Some
drivers in my Windows/System32/drivers folder were
deleted. I copied what I thought might be gone from the
i386 folder on the XP cd (you have to add the last letter
of the extension of each file). I don't remember exactly
what was missing, but what I replaced did the trick.
There's probably a cleaner way to do this, but I couldn't
find one! Good luck!

 

[Guest]

What do you mean I have to add the last letter of the
extension of each file? This make sense, because I
uninstatlled some things right before this happened, but I
don't remember what it was.

 

[Jason Tsang]

Files on the WinXP cd are compressed. You have to expand them before you
can use them. The compressed files have the last letter of their extension
replaced with an underscore so that the compressed files are somewhat
visually identifible.

Regardless, that should not be necessary for errors of this type. There are
easier solutions that I've already posted.