WDS with MDT. Litetouchx64.wim hangs loading files

[petben]

I had a working WDS MDT environment for a few years and now it’s broken. Can’t think of anything that’s changed...

 

F12 boot a client

It gets the IP of the MDT server (WDS is on the same server)

It finds Lite Touchx64.wim and says ‘loading files’ but the progress bar doesn’t move and it fails.

The OS imported to MDT is win10 1809 and all the LAN drivers are added in MDT but I don’t think it’s even getting to MDT?

 

What is it trying to do at this point? I’ve tried restart server and completely regenerate boot image from MDT, then import it to WDS but no luck.

 

Any ideas?

[mullet_man]

Do you get an error after the loading bar?

 

MS recently broke WDS with a Windows update, the fix is in the link.

 

https://social.technet.microsoft.com/Forums/en-US/46e30b31-590e-47b4-b123-faf3776cfe74/windows-update-kb4489882-broke-wds-and-mdt?forum=mdt

[petben]

Thanks, I think it says a general message about possible hardware changes. The MDT server has 4489881 installed but not 4489882, the article starts talking about 4489882 but then people’s replies change to 4489881. I can def try unchecking the ‘Enable Variable Windows Extension’

[mullet_man]

Yes if you get the error about hardware changes after it's loaded the LiteTouch WIM then am 99% sure it's related to this.

 

The different KBs are relating to 2012r2 and 2016 and this affected both I think.

[petben]

Hey mullet_man, you saved the day. awesome.

 

Why MS don't have some kind of alerting system where you can sign up for email alerts on chosen products I don't know..

 

thanks dude

[mullet_man]

Glad you got it sorted [emoji106]

[petben]

Hey mullet_man, our UEFI computers image fine but older computers now are like this:

 

- F12 boot

- The litetouchpe_x64.wim loads

- The Grey 'Windows deployment services' window opens

(it should now do the 'processing bootstrap settings' and prompt for credentials)

- BUT it goes to an empty command window..

 

attached photos.

 

any ideas?

Thanks

[mullet_man]

Am not sure to be honest, is that happening on just one PC have you tried others?

 

Do you have a backup of your older WIM that you used before you regenerated the new one?

 

Am not sure if I've tried to reimage some of our older BIOS devices since that WU, I'll have to check when am back in next week!