can't image ryzen 5 with mdt

[goodheadmcs]

Hi Guys,

Got mdt 2013 setup and it works well on our intel based i series machines.

 

We have just bought some ryzen 5 cpu laptops but won't image properly. The boot image seems ok and copies over the os image but when it comes to the windows getting ready screen with the swirl, it fails with the following.

 

Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft Windows-Deployment].

 

Any ideas please?

[sted]

how are you doing drivers?

try creating a task that only has the correct drivers tagged sometimes ive found on amd machines it can pick an intel driver by accident and fudge things up

[Jaan]

What windows 10 build are you using?

 

Ryzen 5 1000,2000 or 3000

 

I got caught out by this once.

 

https://docs.microsoft.com/en-us/windows-hardware/design/minimum/windows-processor-requirements

Edited November 29, 2019 by Jaan

[goodheadmcs]

Thanks for the suggestion. I added the drivers by a selection profile and its own task but didn't help.

 

I found a post since that said try turning off secure boot in the bios. That seems to have done the trick.

 

Will just turn back on again after the imaging.

 

What windows 10 build are you using?

 

Ryzen 5 1000,2000 or 3000

 

I got caught out by this once.

 

https://docs.microsoft.com/en-us/windows-hardware/design/minimum/windows-processor-requirements

[Arthur]

I found a post since that said try turning off secure boot in the bios. That seems to have done the trick.

 

Will just turn back on again after the imaging.

Are you able to update MDT and ADK to the latest versions and then regenerate your boot images?

 

This will update WinPE so that it support newer processors and you won't have to turn off Secure Boot.

[mrstrong]

Have you checked all the logs for any more info ?

 

e.g. on the client

F8 to bring up command prompt and search for logs via

dir /s/b *.log

from X:\ and C:\

or just get MDT to copy logs to deployment share via SLShare rule

see https://docs.microsoft.com/en-us/configmgr/mdt/troubleshooting-reference