Toshiba Satellite C67cd/dvd disappeared
Closed
mrkhome
Posts
1
Registration date
Sunday September 8, 2013
Status
Member
Last seen
September 9, 2013
-
Sep 9, 2013 at 11:48 AM
xpcman Posts 19530 Registration date Wednesday October 8, 2008 Status Contributor Last seen June 15, 2019 - Sep 9, 2013 at 03:18 PM
xpcman Posts 19530 Registration date Wednesday October 8, 2008 Status Contributor Last seen June 15, 2019 - Sep 9, 2013 at 03:18 PM
Related:
- Toshiba Satellite C67cd/dvd disappeared
- Toshiba satellite touchpad not working - Guide
- Dvd decoder - Download - CD and DVD
- Toshiba satellite factory reset - Guide
- Settings icon disappeared - Guide
- App store disappeared - Guide
1 response
xpcman
Posts
19530
Registration date
Wednesday October 8, 2008
Status
Contributor
Last seen
June 15, 2019
1,826
Sep 9, 2013 at 03:18 PM
Sep 9, 2013 at 03:18 PM
Error Code 32 Troubleshooting
Restart your computer if you haven't already restarted it at least once after seeing the Code 32 error.
There's always the chance that the error Code 32 you're seeing on a device was caused by a temporary problem with the hardware. If so, a restart of your computer might be all you need to fix the Code 32 error.
Did you install a device or make a change in Device Manager just before the Code 32 error appeared? If so, it's likely that the change you made caused the Code 32 error.
Undo the change if you can, restart your computer, and then check again for the Code 32 error.
Depending on the changes you made, some solutions might include:
Remove or reconfigure the newly installed device.
Roll back the driver to a version prior to your update.
Use System Restore to undo recent Device Manager related changes.
Delete the UpperFilters and LowerFilters registry values. One common cause of Code 32 errors is the corruption of two registry values in the DVD/CD-ROM Drive Class registry key.
Note: Deleting similar values in the Windows Registry could also be the solution to a Code 32 error that appears on a device other than a Blu-ray, DVD, or CD drive.
Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is another likely solution to a Code 32 error. This should correctly reset the start type in the registry.
Important: If a USB device is generating the Code 32 error, uninstall every device under the Universal Serial Bus controllers hardware category in Device Manager as part of the driver reinstall. This includes any USB Mass Storage Device, USB Host Controller, and USB Root Hub.
Note: Correctly reinstalling a driver, as in the instructions linked above, is not the same as simply updating a driver. A full driver reinstall involves completely removing the currently installed driver and then letting Windows install it over again from scratch.
Update the drivers for the device. Installing the latest drivers from the manufacturer for a device with the Code 32 error is another possible fix for this problem.
Manually change the driver's start type in the registry. This is the most direct solution to the Code 32 error and should fix the problem if the previous three troubleshooting steps didn't work.
Note: This will likely be the fix if you find the driver's start type in the registry as 0x00000004 which means that it's disabled. The correct start type depends on the driver. For example, cdrom should have a start type of 0x00000001.
Replace the hardware. As a last resort, you might need to replace the hardware that has the Code 32 error.
While not very likely, it is also possible that the device is not compatible with your version of Windows. This might be an issue if the hardware with the Code 32 error was manufactured many years ago or if your operating system is several versions old. You can reference the Windows HCL if you think this might be a possibility.
Note: If you're sure that the hardware itself isn't the cause of this particular Code 32 error, you could try a repair install of Windows. If that's not successful, you could then try a clean install of Windows. I don't recommend doing either of those before you try replacing the hardware, but you may have to give them a shot if you're out of other options.
Good Luck
Restart your computer if you haven't already restarted it at least once after seeing the Code 32 error.
There's always the chance that the error Code 32 you're seeing on a device was caused by a temporary problem with the hardware. If so, a restart of your computer might be all you need to fix the Code 32 error.
Did you install a device or make a change in Device Manager just before the Code 32 error appeared? If so, it's likely that the change you made caused the Code 32 error.
Undo the change if you can, restart your computer, and then check again for the Code 32 error.
Depending on the changes you made, some solutions might include:
Remove or reconfigure the newly installed device.
Roll back the driver to a version prior to your update.
Use System Restore to undo recent Device Manager related changes.
Delete the UpperFilters and LowerFilters registry values. One common cause of Code 32 errors is the corruption of two registry values in the DVD/CD-ROM Drive Class registry key.
Note: Deleting similar values in the Windows Registry could also be the solution to a Code 32 error that appears on a device other than a Blu-ray, DVD, or CD drive.
Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is another likely solution to a Code 32 error. This should correctly reset the start type in the registry.
Important: If a USB device is generating the Code 32 error, uninstall every device under the Universal Serial Bus controllers hardware category in Device Manager as part of the driver reinstall. This includes any USB Mass Storage Device, USB Host Controller, and USB Root Hub.
Note: Correctly reinstalling a driver, as in the instructions linked above, is not the same as simply updating a driver. A full driver reinstall involves completely removing the currently installed driver and then letting Windows install it over again from scratch.
Update the drivers for the device. Installing the latest drivers from the manufacturer for a device with the Code 32 error is another possible fix for this problem.
Manually change the driver's start type in the registry. This is the most direct solution to the Code 32 error and should fix the problem if the previous three troubleshooting steps didn't work.
Note: This will likely be the fix if you find the driver's start type in the registry as 0x00000004 which means that it's disabled. The correct start type depends on the driver. For example, cdrom should have a start type of 0x00000001.
Replace the hardware. As a last resort, you might need to replace the hardware that has the Code 32 error.
While not very likely, it is also possible that the device is not compatible with your version of Windows. This might be an issue if the hardware with the Code 32 error was manufactured many years ago or if your operating system is several versions old. You can reference the Windows HCL if you think this might be a possibility.
Note: If you're sure that the hardware itself isn't the cause of this particular Code 32 error, you could try a repair install of Windows. If that's not successful, you could then try a clean install of Windows. I don't recommend doing either of those before you try replacing the hardware, but you may have to give them a shot if you're out of other options.
Good Luck
