search

FriendsOfMDT / PSD

PowerShell Deployment
MIT License
505 stars 78 forks source link

Stuck on "Just a moment..." Win11 #92

Open laramy2020 opened 1 year ago

laramy2020 commented 1 year ago

I am deploying a semi-custom image of windows 11 It is windows 11 pro dotnet 3.X and 4.x features enabled and fully updated

Image is built in a vm with no extra drivers Image is sysprep-ed and generalized before capture

On deployment with PSD and first reboot i get past getting device ready but then end up stuck on this screen image I have even tried by adding SkipAdminPassword=YES in CS.ini and it still does this. if i force a reboot i get this image then the login screen shows administrator and defaultuser0, i have never touched defaultuser0 at any point of my capture or deployment image

laramy2020 commented 1 year ago

so a workaround/bandaid is to set 2 deprecated values to false in the unattend SkipMachineOOBE and SkipUserOOBE Been digging more into it, I cant tell if this is a PSD unattend issue, or a Microsoft making changes and breaking things issue

laramy2020 commented 1 year ago

So found one reason it can get stuck. If you open the unattend.xml with SIM via the OS Info tab. then save the unattend, the login options get saved in an encrypted format, and they don't match between the admin account, and the autologon section. Even if the password is empty on task sequence creation.

New issue is the OOBE also freezes on just a moment if domain joining is enabled.

laramy2020 commented 1 year ago

I forced rebooted the box. the machine does domain join, but i get the error that the account was incorrect. making me think the unattend is not updated properly to account for the fact the machine is domain joined by the time it needs to log in for oobe

GeoSimos commented 1 year ago

So found one reason it can get stuck. If you open the unattend.xml with SIM via the OS Info tab. then save the unattend, the login options get saved in an encrypted format, and they don't match between the admin account, and the autologon section. Even if the password is empty on task sequence creation.

New issue is the OOBE also freezes on just a moment if domain joining is enabled.

Regarding the encrypted password in the unattend.xml answer file, the encryption is Base64 and you can easily decode the password to check if it matches the one you have set.

GeoSimos commented 7 months ago

I forced rebooted the box. the machine does domain join, but i get the error that the account was incorrect. making me think the unattend is not updated properly to account for the fact the machine is domain joined by the time it needs to log in for oobe

There are high chances that you will face issues with custom build images, can you try deploying via the iso files imported in MDT and add the customizations in the task sequence itself?