sleep versus hibernate versus hybrid sleep

I'm glad it's working now but I do not understand what deleting the Device mgr entry did that simple driver reinstallation did not do.

Now that it is fixed, do consider
Backup and Restore Device Drivers - TenForumsTutorials

When I backup my drivers, which I only do when a driver or piece of hardware has changed, I also make 6 lists of driver & hardware properties using a batch file. This might seem excessive and it has only helped me out of a hole once*** but I do know that there would have been no other solution in that particular case.

Just to avoid a lot of toing & froing, I'll assume you are interested.
The batch file calls Powershell commands which are all built-in and ready.
The batch file also calls three NirSoft utilities - These are 'portable' utilities which means they are not installed; they are merely run as they are.

DriverView - properties of installed drivers
InstalledDriversList - properties of installed drivers [just a slightly different take on the same idea]
DevManView - a Device manager equivalent
I keep each NirSoft utility in a subfolder of its own so I can manage them all easily. Some of them create configuration files [containing user preferences] and using separate subfolders ensures I do not get them mixed up.

This is my batch file - BackupDrivers.bat

Code:

Set BackupFolder=E:\InstallFiles\%ComputerName%\InstalledDrivers
Set NirSoftFolder=C:\Tools\External\NirSoft

:: Export drivers - this is the command suggested in Backup and Restore Device Drivers - TenForumsTutorials
Dism /online /export-driver /destination:%BackupFolder%

:: DriversLists
powershell.exe Get-WindowsDriver -Online ^| Export-CSV '%BackupFolder%\DismDriversList-3rdParty.csv'
powershell.exe Get-WindowsDriver -Online -all ^| Export-CSV '%BackupFolder%\DismDriversList-All.csv'

:: Get HardwareIDs list
powershell.exe Get-WmiObject Win32_PNPEntity ^| Select Name, Manufacturer, DeviceID, Status ^| Export-CSV "%BackupFolder%\HardwareIDs.csv"

:: Get DriverView output
%NirSoftFolder%\DriverView\DriverView.exe /scomma "%BackupFolder%\DriverView.csv"

:: Get InstalledDriversList output
%NirSoftFolder%\InstalledDriversList\InstalledDriversList.exe /scomma "%BackupFolder%\InstalledDriversList.csv"

:: Get DevManView output
%NirSoftFolder%\DevManView\DevManView.exe /scomma "%BackupFolder%\DevManView.csv"

- You need to alter the lines beginning Set BackupFolder and Set NirSoftFolder to match where you want to put things
- You can omit any lines that you do not intend to use.
- I use csv file outputs because they can be opened in Excel & searched/manipulated as required.
- I created the folder C:\Tools as a repository for all my scripts [batch files, PS, VBS, external third-party 'portable' utilities such as NirSoft ones] and protected it in the same way that, for example, C:\Program files is protected. I used the procedure in Set up my Tools folder ditty - TenForums

Denis

---

*** These lists helped me out of a hole once. I have only described the details so you can understand how rarely my driver backups are useful yet how essential they are.
- I got a new computer.
- I made a system image then backed up the drivers & made the driver properties lists I've mentioned.
- I reinstalled Windows. Irrelevant comment - I reinstalled to remove Android as it was originally a dual-boot Windows & Android device.
- I worked through all the driver installation files provided by the maker [Chuwi, from whom I would never buy again].
- I made a new system image then again backed up the drivers & made the driver properties lists I've mentioned but to a different %BackupFolder% so I kept the original driver backups intact.
- The built-in camera did not work. The touchscreen did not work correctly.
- I worked through my driver properties lists and discovered that the maker had provided the correct drivers in the computer at purchase but their driver download file contained drivers for the wrong devices [and still does].
- I worked through the driver properties lists to confirm the HardwareIDs of the problem devices then looked up the corresponding entries in the original driver backup by cross-referencing entries in the various lists. Doing all this involved using 4 of my 6 driver properties lists so I concluded that going overboard on these lists was worthwhile.
- Having positively identified them, I installed the drivers for the problem devices from the original driver backup.
- The camera worked. The touchscreen worked correctly.
- I have, since then, posted the correct drivers online for six other users who had not made driver backups of their own. They had been struggling for quite some time and had found no other solution.