Member Avatar for Radio2006

Hello all,

My enterprise just released Windows 10 on one of our domains. Using the previous Windows 7, we were able to sysprep a copy of the OS pulled down from SCCM by imaging a workstation with a task sequence.

Continuing with that practice on Windows 10 has presented some issues. I have worked through the sysprep issues, but when attempting to boot the workstation using one of the replicated HDD's, we run into issues.

1: Upon initial bootup we get an error stating that the installation could not be "configured". To continue, restart the workstation.

We were able to get around this issue by forcing a safe mode boot. THe workstation begins to install drivers and get devices ready. However, after a few minutes, we get this error:

2: Windows cannot complete the installation. To continue the installation, restart the workstation.

We have had no luck getting past this issue. We have attempted to "press F10 and Shift+f10 and all the other "F" keys with no luck. I have been searching for answers for days and cannot figure out why the process nor the recommeded fix actions are wokrking.

Side note: Our IT is broken up into many parts...we have a division that creates the images and another that deploys the images to SCCM, so I do not any power to make changes; I can only work with what I have.

Any and all assistance would be greatly appreciated and thanks in advance.

  • 3 Contributors
  • 4 Replies
  • 664 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by SN Technologies

Dani AI

Generated

Short, practical guidance tied to the existing thread (for , building on and ): start by gathering the setup/sysprep logs before changing anything — the most useful files are under C:\Windows\Panther and the Sysprep folder (these show OOBE/Sysprep errors and the package names or steps that failed). If Shift+F10 isn’t available on the stuck machine, boot from Windows install media → Repair → Command Prompt to access those logs. (learn.microsoft.com)

Common root cause and what to check next: many modern Windows images fail final OOBE because AppX (Microsoft Store) packages were updated or left installed for a user but not provisioned for all users. Sysprep/setuperr will name the offending package; remove it and its provisioning before you generalize the image. In Audit mode (or on the reference VM) use PowerShell to list packages, remove the specific package, then remove the provisioned package from the image. Example (adapt to the exact PackageFullName you find in the log): 

Get-AppxPackage -AllUsers | Format-Table PackageFullName,PackageFamilyName
Remove-AppxProvisionedPackage -Online -PackageName "<PackageFullName>"

Follow the MS guidance for Appx/provisioned-package removal before running Sysprep. (learn.microsoft.com)

If you’re already at the OOBE dialog and nothing progresses, a widely used in-place workaround is to open Repair → Command Prompt → regedit and set
HKLM\SYSTEM\Setup\Status\ChildCompletion\setup.exe = 3 (or run reg add "HKLM\SYSTEM\Setup\Status\ChildCompletion" /v setup.exe /t REG_DWORD /d 3 /f) — this forces setup to continue. Use this only as a recovery step and capture the logs afterwards. (windowsdigitals.com)

Because the image was deployed from SCCM, also check for OSD leftovers: HKLM\SYSTEM\Setup\CmdLine, %WINDIR%\Setup\Scripts\SetupComplete.cmd, _SMSOSDSetup folders or osdsetuphook.exe hooks — cloning a drive mid-task leaves the image waiting for the task-sequence pieces and will hang OOBE. If you cannot change the golden image, collect the logs and the exact package names/errors and hand them to the imaging team (they’ll need those items to rebuild the master image). (recastsoftware.com)

Recommended Answers

All 4 Replies

Member Avatar for rproffitt

This only works if the target PCs are clones of each other. For other than that, you need to install for each model and develop an image suitable for each PC model.

Member Avatar for Radio2006

rproffitt,

Understand all. Unfortunately, that is what we are doing. Imaging a workstation, sysprepping it, replicating it, then using one of the newly copied hard drives and installing it in the same workstation.

Member Avatar for rproffitt

Neat. That's what many do and works. If it doesn't back to the beginning and find out why. Such is the life of IT. Sometimes you go over your training notes or call Microsoft to have them tell you why it won't work in this case.

Member Avatar for SN Technologies

Howdy rproffitt, thanks for the advice, I was also having the same kind of configuration issue and now will try with your idea. probably same might be the reason why we aren't able to configure it properly and now we can try doing so without replicating other systems.

Thanks alot once again.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.