Table of Contents
Identifying the Hardware Driver ID
One of the first steps, when you encounter the issue of the computer being unable to turn this device to save power, is to identify the hardware driver ID. Knowing the ID of your hardware driver can allow you to troubleshoot effectively. Here's how you can find out:
Opening the Device Manager
Firstly, use the Windows shortcut keys Win + X to open the quick-access menu. Then select the 'Device Manager' from the list. This utility allows you to view and control the hardware attached to your computer. You will be able to see a list of all your hardware drivers.
Locating and accessing the problematic device driver
Expand the hardware categories by clicking on the right-arrow mark to locate the hardware with the power saving issue. Once you find it, right-click on the problematic driver and click on 'Properties'. This will open up a window with detailed information about the selected hardware driver.
Checking and copying the Driver Key
After accessing the driver properties, select the 'Details' tab. By default, the Device description will be displayed. You have to click on the dropdown menu and switch it to 'Driver Key'. This will display the driver key or the driver ID in a string format. You can copy this key and save it. This hardware driver ID can provide essential insights for complicated troubleshooting that involves power related issues.
Toggling the PnPCapabilities Key
What makes the Windows Operating System quite versatile is its ability to modified through the Registry Editor. This editor has vast capabilities, including the ability to potentially rectify the issue of the computer not allowing you to turn off a device to save power. You need to be very careful, however, as a slight misstep could lead to other issues. Here's how to proceed:
Opening the Registry Editor
To open the Registry Editor, press the Win + R shortcut keys to open the Run dialog. In this dialog box, type 'regedit' and press Enter. This action will open the Registry Editor in a new window.
Creating a system registry backup
Before initiating any changes in the registry editor, it's always wise to create a backup of your system registry so that significant issues can be avoided in case of an error. You can do this easily by clicking on 'File' and opting to 'Export'. In the export registry window, choose a location to save the backup file and give it a name. Now, your registry backup has been created.
Navigating to the specific location of the Driver Key
Now, navigate through the navigation tree to this address: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Class > {36fc9e60-c465-11cf-8056-444553540000}\0005
Note: The part '{36fc9e60-c465-11cf-8056-444553540000}\0005' should be replaced with the driver key you copied earlier from the Device Manager. This will lead you to the device where you face the power saving issue.
Creating or modifying the PnPCapabilities D-Word value
Now find the PnPCapabilities key in the right pane of the Registry Editor window. If this key doesn't exist, you can create it by right-clicking in a free space and selecting 'New'>'DWORD (32-bit) value'. Rename the new registry key as 'PnPCapabilities'.
Setting the PnPCapabilities value to “0”
Double-click on the PnPCapabilities key you created or found and change its value data to '0'. This action should enable the power saving option in the Device Manager for your device.
Running the Hardware and Device Troubleshooter
If the above methods failed to solve the issue, you could try running the Hardware and Device troubleshooter provided by Windows as a default feature. It's an effective tool designed to detect and potentially fix hardware-related issues on your system. Follow these steps to run the troubleshooter:
Opening the Run Panel
The first step to running troubleshooting involves opening the Command Prompt. Press Win + R to bring up the Run panel. Next, type 'cmd' in the entry field and use the shortcut Shift + Ctrl + Enter to open command prompt as an administrator. Remember to grant the necessary permissions if any prompted to continue.
Starting Device Diagnostics
In the Command Prompt window, input the line 'msdt.exe -id DeviceDiagnostic' and then press Enter. This command will open the Hardware and Device troubleshooter, ready to start diagnosing potential issues with your device.
Applying recommended solutions
After the troubleshooter has done scanning, it will report any detected issues. Click 'Next' and follow the subsequent instructions to apply the recommended fixes. By doing so, any issues causing the power-saving option to be grayed out might be solved. If the troubleshooter fails to start or is missing, you might need to seek an advanced solution or technical help.
Uninstalling and Reinstalling the Device Driver
If your issue is still persisting, then you may need to consider uninstalling and reinstalling the device driver. Sometimes, erroneous power management settings can occur due to faulty or outdated drivers. Follow the steps below to accomplish this:
Finding the affected device in the Device Manager
Initially, you need to locate the affected device. To do this, press Win + X and choose Device Manager from the quick access menu. Once the Device Manager window opens, expand the 'Universal Serial Bus controllers' category. Here, you will find the driver for the problematic device.
Uninstalling the driver and restarting the computer
Right-click on the problematic driver and choose 'Uninstall device'. A confirmation dialog will appear, click 'Uninstall' again to confirm. If the "Allow the computer to turn off this device to save power" option is grayed out for multiple devices, you might need to uninstall their drivers as well. Once you have uninstalled the necessary drivers, restart your computer to effect the changes.
Waiting for Windows to automatically reinstall the driver
Upon restarting, Windows should automatically scan for hardware changes and reinstall the uninstalled drivers. With the freshly installed drivers, check if the power saver management setting is available now. If so, then the problem was with the previous drivers and it has been successfully resolved. If not, you may need additional assistance or attempt advanced troubleshooting procedures.
