0 Members and 1 Guest are viewing this topic.
Figured it out. It's because I was using Remote Desktop to access the PC. Apparently when you use RDC it disables burning. I can't figure out why they would make it work that way (or how to change it). After physically logging into the PC it worked fine. The strange thing is that in the beginning when I was having this problem, I wasn't RDC'd into the computer at the time. After it started working again, I was using RDC and that's when it seemed like the problem reappeared.Thanks for the help in any case everyone.
Press the Windows logo key + R to open the Run dialog box. Type regedit in the Run dialog box, then press Enter. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318} In the right pane, click UpperFilters. Note You may also see an UpperFilters.bak registry entry. You do not have to remove that entry. Click UpperFilters only. If you do not see the UpperFilters registry entry, you still might have to remove the LowerFilters registry entry. To do this, go to step 7. On the Edit menu, click Delete. When you are prompted to confirm the deletion, click Yes. In the right pane, click LowerFilters. Note If you do not see the LowerFilters registry entry, go to the next resolution. On the Edit menu, click Delete. When you are prompted to confirm the deletion, click Yes. Exit Registry Editor. Restart the computer.
That is a interesting find. I wouldn't have guessed that ShellHWDetection Service would have anything to do with the cd drive showing up as a burner lolShane
Have you checked to see what a sfc /scannow reports with and without it enabled ?
Perhaps it's because you have been playing around with the files that you are getting the error messages that you are and it's time to put them back to the way Windows prefers ?