WinPE: Find missing drivers: Unterschied zwischen den Versionen
Aus Wiki-WebPerfect
Admin (Diskussion | Beiträge) |
Admin (Diskussion | Beiträge) |
||
| Zeile 3: | Zeile 3: | ||
=== Find missing drivers === | === Find missing drivers === | ||
| − | [[Datei:01-wbemtest.png|right| | + | [[Datei:01-wbemtest.png|right|700px]] |
*'''Open a remote console''' (iLO for example) of the system that stucks in the WinPE deployment. | *'''Open a remote console''' (iLO for example) of the system that stucks in the WinPE deployment. | ||
*Press '''Shift + F10''' to open CMD. | *Press '''Shift + F10''' to open CMD. | ||
| Zeile 12: | Zeile 12: | ||
*Now you can see all devices in an error state. | *Now you can see all devices in an error state. | ||
*You can see the device when you '''double click on an entry''' and in '''properties''' scroll down to '''Caption'''. <br> | *You can see the device when you '''double click on an entry''' and in '''properties''' scroll down to '''Caption'''. <br> | ||
| − | [[Datei:02-wbemtest.png]] | + | [[Datei:02-wbemtest.png|right|700px]] |
[[Kategorie:Windows]] | [[Kategorie:Windows]] | ||
Version vom 15. Juni 2020, 12:25 Uhr
If you boot from a WinPE image, for example in a baremetal deployment workflow, and the deployment stuck, the reason for this is maybe missing drivers.
In this article you can learn you to find missing drivers in an WinPE image.
Find missing drivers
- Open a remote console (iLO for example) of the system that stucks in the WinPE deployment.
- Press Shift + F10 to open CMD.
- Open Windows Management Instrument Tester: Run wbemtest in CMD.
- Press Connect... and check the Namespace. It should be root\cimv2
- Press Query... and run following query
select * from win32_pnpentity where status LIKE ‘%error%’
- Now you can see all devices in an error state.
- You can see the device when you double click on an entry and in properties scroll down to Caption.
