Windows 10: Not sure if I should use /generalize and/or /oobe with sysprep to clone install to a new PC.

I have a Windows 10 64 bit install I forgot which build, I think it was 1909 from a 3770K system that is giving me issues that I want to migrate over to a new 10700K system that I built. Since this was a sudden issue the 3770K system started giving me and I have many years of settings I want to keep, I wanted to see if it was feasible to clone the install to the new system before starting over. From what I read, sysprep is what I want for that. Only issue is I am not sure what options to use. I do want to wipe the drivers and any hardware-specific settings/configurations which from wh

:)

 

Windows 10 - How To Create A Generalized Image With Sysprep?

That audit step isn't necessary. It is possible to install apps with user ID ('User1') which is created when OS is installed firs time and then run Sysprep /oobe /generalize /shutdown.

On drawback with this shortcut is that created image has already this 'User1' existing and it can't be used on new installations. On small environment with few PC's this 'User1' can be local admin which will be automatic on all new installations. End users
can be 'User2', 'User3' .. without admin rights. This work fine with few PC's where installations is made 'manually' with USB installer.

With large systems where installations are done over network using deployment server it would be better to use sysprep audit mode. Then system boot using system default Administrator (which is not activated by default). Now it's also possible to add apps
and remove 'User1' before continue sysprep with OOBE. This way captured image don't have any users preinstalled and all new installations are 'clean'.

 

Windows 10 Update breaks Sysprep?

I am attempting to image a Dell E7470 with Sysprep to upload to my WDS server.

When I run Sysprep /oobe / shutdown, it completes. However, without Generalize, I won't be able to upload it or deploy it.

When I run Sysprep /oobe /generalize / shutdown, it reports that a fatal error has occurred. The setupact.log lists that the Miracastview app cannot be removed.

I have attempted the Remove-appxpackage commands, but it states that it has been provisioned for the user but not all users. It says to attempt removal with Add / Remove Windows features, but it is not listed there.

I have tried the steps in

MiracastView cause sysprep error in Windows 10 Version 1709 - Windows Client

but none of this has worked either.

I guess the answer is to not run any Windows updates before Sysprep and avoid 1709? It appears to be bad news.

Anybody else encounter this? Any other solutions available?

 

Windows 10 OOBE loop after sysprep

I ran into boot loop after sysprep Windows 10.

I've prepared a custom machine to deploy with WDS.

Sysprep has been run with /oobe/generalize options.

When I restart, windows 10 get into a reboot loop, and every time ask for system oobe wizard.

I found these on setuperr log file:

[msoobe.exe] Failed to set password and password hint with hr=0xD000006C

[msoobe.exe] Failed to create the default account with hr=0xD000006C

[msoobe.exe] TASK: End failed running task PrepareUserOOBE with hr=0xD000006C.

[msoobe.exe] Failed user OOBE prep task with hr=0xD000006C

[msoobe.exe] Failed to run OOBE Host with hr=0x80004005

[msoobe.exe] OOBE failed with hr=0x80004005

[windeploy.exe] Command [%windir%\system32\oobe\oobeldr.exe /system /quiet] failed with exit code [0x80004005]

[windeploy.exe] OnError commands failed. hr = 0x80070002