ITGURU Posted September 18, 2023 Posted September 18, 2023 I've setup and been configuring MDT for Windows 11 deployment over the weekend. Created a Win11 VM on Hyper-v captured it, restored it successfully and added to network and all working fine as expected. Today have restored the image to a bare metal machine, and got the error below. I then created a new image on a physical PC, captured it , restored it, but then got the same error. please could anyone advise/assist why capture/restore on VM works, but capture, restore or restore of any image to physical hardware fails with the above error in photo? thanks.
ITGURU Posted September 18, 2023 Author Posted September 18, 2023 Just an update - I have restored the physical machine captured image back to the Hyper-V VM and that's restored absolutely fine, so appears to be an issue restoring any image to a physical machine.
3s-gtech Posted September 18, 2023 Posted September 18, 2023 Do you need to do this with fat images? I ditched fat when I went to MDT back in 2020, and have never missed it. Don't get me wrong, thin is sometimes slow - but being able to update images in modules is awesome. My task sequences just get a new WIM in them when one comes out.
snagrat Posted September 18, 2023 Posted September 18, 2023 (edited) That is a known error with MDT and the ADK version when used with BIOS devices. https://support.microsoft.com/en-us/topic/windows-10-deployments-fail-with-microsoft-deployment-toolkit-on-computers-with-bios-type-firmware-70557b0b-6be3-81d2-556f-b313e29e2cb7 But thin images is still the way to go, easy to change OS media when there is an update etc. If it is a newer machine then may be worth resetting the BIOS to factory settings to ensure stuff like SecureBoot hasn’t been disabled in the past Edited September 18, 2023 by snagrat
Jobos Posted September 18, 2023 Posted September 18, 2023 There’s a fix for that something like running a script part way through the task and had it myself with MDT. I’ll dig it out tomorrow.
ITGURU Posted September 18, 2023 Author Posted September 18, 2023 This is windows 11 and EUFI BIOS That is a known error with MDT and the ADK version when used with BIOS devices. https://support.microsoft.com/en-us/topic/windows-10-deployments-fail-with-microsoft-deployment-toolkit-on-computers-with-bios-type-firmware-70557b0b-6be3-81d2-556f-b313e29e2cb7 But thin images is still the way to go, easy to change OS media when there is an update etc. If it is a newer machine then may be worth resetting the BIOS to factory settings to ensure stuff like SecureBoot hasn’t been disabled in the past
bknaggs Posted September 18, 2023 Posted September 18, 2023 All drivers for the PC available for both Windows 11 and Windows PE?
ITGURU Posted September 18, 2023 Author Posted September 18, 2023 What ADK version you using? ADK - 10.1.22621.1 ADK Windows PE 10.1.19041.1 both are versions for windows 11 22H2 and thats the version i'm deploying/capturing.
Jobos Posted September 19, 2023 Posted September 19, 2023 May not be relevant with the fix @snagrat posted but I'm using the same version of MDT I started using with win10 and I added the script when I got the same error. I've left the script in place and it still works with win11. It's an old video but it works.
stevewill6 Posted September 19, 2023 Posted September 19, 2023 Had the same problem yesterday with windows 11 deployment to "older laptops" Added the check to the task sequence and now working well.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now