![]() |
|
|
#3 | |
|
Member
Join Date: Dec 2016
Posts: 39
|
Quote:
What's the point of hiding the separate .INF and .MSI packages behind a corporate download portal? Could you please add the .INF and .MSI packages to the standard public download page? Tried it. Injecting all the .INF files into the boot.wim of WinPE 10.0.14393 as per the MSDN instructions was working. However: - The .INF files of driver version 8.2 M1 did cause WinPE 10.0.14393 to hang upon booting or even showing BSODs upon booting - The .INF files of driver version 8.0 M3 still caused WinPE 10.0.14393 to hang upon booting sometimes, but succeeded in booting most of the time and did not produce BSODs - Once booted, the network did work (which it did not previously without the injected .INF files) - The monitor did not work (or it wasn't active at least, obviously WinPE does not have a GUI to choose which monitor should be used, maybe the monitor would work if one could choose which monitor should be active, not sure) Thank you, would be interesting. Last edited by qp6019352; 05-17-2017 at 01:34 PM. |
|
|
|
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|