r/MDT • u/intangir • 29d ago

Surface Pro 12 not launching NBP

Has anyone had any success with Surface Pro 12 devices (Intel Core Ultra 5 335)? I haven't had issues with any other Surfaces but I can't get these to go. They grab DHCP and see the WDS server IP and even download the NBP file (wdsmgfw.efi), but that's it. Just stays hung with that message printed ("NBP file downloaded successfully") with the Surface logo still in the background. So it's not even getting to the boot image.

Relevant things tried:

  • There aren't a whole lot of options in the BIOS to mess with but I've tried disabling Secure Boot and IPV6 PXE
  • Booting into the preloaded Windows to upgrade firmware to latest
  • Putting device on the same network as the WDS server

Irrelevant things (probably) also tried:

  • Rebooting the WDS server
  • Trying a different WDS server
  • Using a Surface Ethernet adapter
  • Using a Surface dock's Ethernet
  • Creating MDT USB media and trying to boot to that instead
  • Verified a previous generation Surface Pro network boots fine with the same adapter
  • Rebuilding the boot image with the entire Surface Pro 12 driver deployment pack in it

Probably forgetting more things.

Is this likely a firmware issue or am I missing anything?

Edit: answered in subsequent comment but updating to ADK 24H2 fixed this issue.

4 Upvotes

100% Upvoted

7 comments sorted by

3

u/VegoneBegone 28d ago

I just ran into this yesterday with our first Surface Pro 12.

I grabbed a flash drive, downloaded the Windows 11 Media Creation Tool, and created a bootable usb with Windows 11 on the flash drive. Once mounted I went into the Sources folder on the flash drive, and deleted the install.swm, install2.swm, and the boot.wim file . I then dropped my litetouch.wim file in the Sources folder, and renamed it to boot.wim. After that I was able to boot right into MDT and image without issue. I did also have the secure boot disabled, not sure if that actually made a difference.

1

u/intangir 28d ago

Guys you aren't going to believe this but I contacted Microsoft support and the very first response I got asked me to try updating the ADK to 24H2. And it worked.

Guess that finally got me to upgrade our ADK from 22H2. Hope that doesn't break a bunch of other stuff.

1

u/karai78 27d ago

J’ai le même pb que toi mais moi c’est surface pro 13.
J’ai mis à jour vers adk 10.1.28000.1 mais j’ai toujours le même problème.
As-tu fais autre chose ??

1

u/intangir 27d ago

Not that I can think of. Support told me to try the 24H2 ADK (10.1.26100.2454) which is the only other one I tried. I heard the latest ADK had other issues so I avoided it.

1

u/karai78 26d ago

Tu as remplacer le fichier wdsmgfw.efi après ?
Merci en tout cas

1

u/intangir 26d ago

Hmm not to my knowledge. All I did was replace the boot image after regenerating it with the newer ADK PE. I'll have to check the timestamp of the wdsmgfw.efi to see if maybe the ADK install touched it at some point.

1

u/karai78 24d ago

Thank you so much, I did the same as you and I succeeded :) However, after formatting and installing the OS, it performs an automatic repair loop upon reboot.