Code 41 with a New DVD Burner

This is a technical article to help somebody if they have the same problem I did. If somebody hits this via a Google search, I hope this helps. For everyone else, you probably can skip this one.
So our old DVD burner (a NEC ND-3520A) on our computer died. It had long ago stopped burning or playing CDs, and finally stopped being recognized at all. So we replaced it using a gift card my company gave us.
After some research I decided on a Samsung SH-S223F that we picked it up from New Egg for $25. It amazes me that drives of far less quality sell at Wal-Mart even for far more, even after shipping and handling was added to the order. The S223F is a very fast drive and is SATA over the older IDE which was something I really wanted.
Anyhow the computer recognized the drive quickly and everything was going well, Windows detected the new hardware but it never showed up in My Computer. When I looked it up in Device Manager it has a yellow astrix next to it and said it was a code 41.
What I eventually found was a Russian page that helped me fix the problem, but since then I found a Microsoft Support page that gives the same details in English without needing to use Google’s translation service. That page covers errors 31,31, 19, 39 and 41. In short the registry LowerFilters and UpperFilters in HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Class/{4D36E965-E325-11CE-BFC1-08002BE10318} need deleted, a process I’ll leave to the aforementioned MS support page to explain. I can’t tell exactly what UpperFilters and LowerFilters are in the registry though it looks like it relates to how burning software interacts with the burner. Most software installs it’s own filters at the software level, but MS for some reason puts it in the registry which can cause occasional conflicts. Let’s hope they fix this in Windows 7… I doubt it, like I doubt they fixed Windows long term problem with the clock (International PC standards have long required the PC clock to be set to UT, with the OS adjusting it to the local time, and all OSs except Windows follow this standard, while Windows sets the PC clock to local time, this causes a problem in dual boot situations).