I told Lenovo and their stuff is good to go now. Windows Primary (C:) NTFS 99% of remaining We regenerated the SCCM Deployment task sequence FRESH from the default (SCCM 1902) and noticed the Apply Image step was creating partitions in a different order than the one we'd been carrying over since Win 8.0.
That worked, but if i replace install.wim with an MDT image (slimmed down from normal). Same thing.Īlso tried generating one of those Windows 1903 boot keys you make online. We also give our image to Lenovo and they apply it to our PCs at the factory. This happens on multiple Thinkpad models current, last year, 2015, etc. Not sure why it doesn't fail on type 2 HyperV withe secure boot enabled. Which explains why i don't get the issue on type 1 HyperV. If there is a question this is UEFI, nobody uses legacy BIOS outside of VM these days. At that point it also will not boot WinPE based on 1903 altough WinPE based on earlier windows releases, 1809, 1709, 1511 boot fine. Every PC i build with the 1903 imageīoots once, does some setup work, then reboots to the boot selection menu. Changes we've done for 1903 include the OS, MDT and ADK version. We've been making MDT images and deploying with SCCM since Win8.
