Quote:
Originally Posted by AlbanRampon
you can look in the Corporate Deployment section. Then, download the .INF based package. In it, you will have a folder called Win10RS1-RS2 including both the 32- and 64-bit drivers.
|
Aren't these the same .INF files that come with the .EXE?
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?
Quote:
Originally Posted by AlbanRampon
Should you have time and willingness to try
|
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)
Quote:
Originally Posted by AlbanRampon
I'll ask tomorrow night if my contact at Microsoft knows if WinPE has the underlying graphics structure.
|
Thank you, would be interesting.