Sysprep error windows is unable to start

Updates can all be "slipped in" with offline servicing ahead of time, along with several other modifications to the WIM.

We are incredibly time sensitive re: OSD. Offline servicing sadly does not do Office updates. Hence our need to build and capture. If you're using M Adds like minutes to install M during deployment. Thanks for your time. If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

If possible, we could try to build the reference workgroup computer with Office and Windows updates firstly. And then use the Capture Task Sequence Media to capture your reference image. Hi, Another tip..

I have the same question 4. Report abuse. Details required :. Cancel Submit. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Windows 10 inherited activation not working. How can i download older version of Windows Version iso file.

I can't update my PC to Update. Skip to main content. Find threads, tags, and users Current Visibility: Visible to all users. Edit: Solution for now , copied from my comment below. Glad you were able to get it working!

I'm glad I wasn't the only one experiencing this issue. Thank you for the solution, worked like a charm. Very frustrating though Great solution, worked perfect! Keep up the good work. Comment Show 0. Hi, The issue you are facing is a known issue. Hi, Installing new Microsoft Store apps or updating your existing Microsoft Store apps before generalizing a Windows image will cause Sysprep to fail.

After doing the sysprep with not clicking start at all, it fixed everything for me! Good luck. Very frustrating. I looked it up online and tried all the solutions, but so far none of them work. This package will not function properly in the sysprep image. It is because you tried to remove some of the bloatware apps and the windows store is not disabled and it tries to update the apps during sysprep. When you delete the bloatware make sure to un-provision the app too.

When I build my image I create a base user first. Then open Administrator account log in as administrator delete other user via control panel never connecting to the internet until this is completed. It avoids apps from being updated as apps can not run on administrator to be updated. Plus to be safe I only connect to internet to pull the image via sccm and apply updated in sccm console. Travis FTFY! User appx packages need to be removed from the account before a sysprep.

Also - do not login as any domain accounts beforehand, use a local admin. I had the same issue.