Unable to Sysprep (Win 10 Pro version 1809)

[Sonic3]

I am at my absolute wit's end with this issue I've been having when trying to use Sysprep in Win 10 1809. I have exhausted my web searches and all the "solutions" and so I'm really hoping someone here has a better idea of what to do.

 

When trying to run Sysprep, I'm getting the following error message in the 'setupact.log' file:

 

SYSPRP Package Microsoft.XboxApp_44.44.7002.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.

 

That's fine, I thought, I'll just remove the XboxApp app using 'Remove-AppxPackage' in PowerShell which seems to work but Sysprep fails with the same error, and on using 'Get-AppxPackage' I can see that the XboxApp app is still there.

So I tried 'Remove-AppxPackage -AllUsers -Package Microsoft.XboxApp_44.44.7002.0_x64__8wekyb3d8bbwe' and I get this error:

 

Remove-AppxPackage : An error occurred because a user is logged off

 

On further investigation, the user it's referring to was a local admin account that has since been deleted.

 

From this, I've been scouring the web for solutions for 2 whole days but nothing is working. Is this just Win 10 1809 being broken? I really don't want to have build up a whole new image again! Any ideas?

[free780]

Can you not just leave the apps as default and build and capture? I try and automate it in MDT so I can repeat the process. It's easier unprovisioning the apps when the image is applied.

[Sonic3]

Can you not just leave the apps as default and build and capture? I try and automate it in MDT so I can repeat the process. It's easier unprovisioning the apps when the image is applied.

 

Thanks for the reply but I'm not really trying to remove the apps. Sysprep is failing due to the XboxApp app being installed for a single user (rather than all users), so removing the app is supposed to be a solution. If there's another way to get sysprep to work then great! I just can't find anything that works

[mikkydoos]

I had problems with LTSC 1809 not sysprepping.... try this in this order...

 

 

get-appxpackage -allusers | select name, packagefullname

 

 

-------->

 

Get-AppxPackage %%%packagefullname%%% | Remove-AppxPackage -allusers

 

 

 

*****packagefullname****** == NOT the FULL package name but the 'title' of the package name

 

 

 

e.g. Microsoft.XboxApp or whatever is listed in the lefthand column after running get-appxpackage.

 

 

 

If that doesn't run with some kind of output from PS, it hasn't executed. I got this working by running this using the user I first logged on with.

 

 

A bizarre and convoluted remedy but it worked for me.

 

 

 

 

The syntax in this link is different to Microsoft's documentation but it works...... https://www.askvg.com/guide-how-to-remove-all-built-in-apps-in-windows-10/

Edited April 9, 2019 by mikkydoos

[Arthur]

If there's another way to get sysprep to work then great!

Temporarily disable app updates or prevent the VM you are creating the image on from accessing the Internet.

 

Fixing why Sysprep fails in Windows 10 due to Windows Store updates

 

When creating reference images for Windows 10, Sysprep is going to fail if the machine have Internet access, and have enough time to start updating it’s built-in applications, or install new ones as part of the consumer experience feature. This post is about preventing that from happening, and is a companion to uber-guide on building Windows 10 reference images in the real world:

 

The issue is explained in a KB from Microsoft, but it’s workaround are not very good for automation purposes.

 

Alternatively do not sysprep at all. Modify the install.wim offline. e.g. with OSDBuilder.

[Sonic3]

I had problems with LTSC 1809 not sysprepping.... try this in this order...

 

etc.

Thanks, but although 'Get-AppxPackage Microsoft.XboxApp | Remove-AppxPackage -allusers' seems to work (no error output), sysprep fails with the same error message as before and when running 'get-appxpackage -allusers | select name, packagefullname' again the XboxApp app is still on the list!

I can't log in as the user account that installed it because the account has been deleted.

 

 

Temporarily disable app updates or prevent the VM you are creating the image on from accessing the Internet.

 

(etc.)

 

Thanks but this is how to prevent it happening next time (which I understand might end up being my only option) but I really don't want to have to start the build process again :/

[MYK-IT]

Still testing / finalising Windows 10 build ourselves, but have recently overcome this particular problem using a combination of what @Arthur has already suggested and using the 'Invoke-RemoveBuiltinApps. ps1" script (within MDT build process) located at https://www.scconfigmgr.com/2018/11/27/remove-built-in-apps-for-windows-10-version-1809/

[Jobos]

@Sonic3 was this a fresh install of 1809 or upgraded to 1809? If upgraded what was the original version?

[Sonic3]

Still testing / finalising Windows 10 build ourselves, but have recently overcome this particular problem using a combination of what @Arthur has already suggested and using the 'Invoke-RemoveBuiltinApps. ps1" script (within MDT build process) located at https://www.scconfigmgr.com/2018/11/27/remove-built-in-apps-for-windows-10-version-1809/

 

Thanks. Trying this now...

[Sonic3]

@Sonic3 was this a fresh install of 1809 or upgraded to 1809? If upgraded what was the original version?

 

Completely fresh install of Windows 10 Pro for Workstations 1809 downloaded from the Volume Licensing Service Center.

[Sonic3]

Still testing / finalising Windows 10 build ourselves, but have recently overcome this particular problem using a combination of what @Arthur has already suggested and using the 'Invoke-RemoveBuiltinApps. ps1" script (within MDT build process) located at https://www.scconfigmgr.com/2018/11/27/remove-built-in-apps-for-windows-10-version-1809/

 

According to the log file for that script:

 

Unable to locate AppxPackage for app: Microsoft.XboxApp

Unable to locate AppxProvisioningPackage for app: Microsoft.XboxApp

Unable to locate AppxPackage for app: Microsoft.XboxGameOverlay

 

Removing application provisioning package: Microsoft.XboxGameOverlay_1.39.29002.0_neutral_~_8wekyb3d8bbwe

 

And then it just hangs.

 

If it's unable to locate the AppxPackage then that explains why it's not removing properly. Any idea what can be done about this?

[Achandler]

If you add a new user, then delete the profiles of all the others then it will probably work. It's basically if you click or touch the apps in anyway then it can't be sysprepped.

[FragglePete]

Over the many years of Sysprep-ing, they seem to change things without really detailing what's changed. But, from experience I've found that you can't Sysprep a machine if it's joined on the Domain, and I leave all the Appx's as is and remove the ones I don't want as part of the MDT Sequence. Both of these caught me out a while back.

 

The only thing I'm doing to a captured image is purely windows updates and installing USBDLM. Everything is done on the MDT especially Office365 using Device Based Activation.

 

Just finalised our 1809 image so we have something ready, but waiting for 1903 now.

 

Pete

[KEVIA]

If you add a new user, then delete the profiles of all the others then it will probably work. It's basically if you click or touch the apps in anyway then it can't be sysprepped.

 

This solution fixed it for me, deleted all profiles and left local admin. Worked like a treat!

[mikkydoos]

This solution fixed it for me, deleted all profiles and left local admin. Worked like a treat!

 

 

That will probably do it. And get it off the domain... although I prepped one of my images whilst joined. Worked ok.

 

 

EDIT: Download GeekUninstaller and see what it lists as installed apps - you can use this to remove provisioned apps as well as using get-appxpackage

Edited April 9, 2019 by mikkydoos

[Sonic3]

If you add a new user, then delete the profiles of all the others then it will probably work. It's basically if you click or touch the apps in anyway then it can't be sysprepped.

 

Sadly this didn't work for me. Same error message in the sysprep log file. Is there any way to reinstall the Xbox app for all users so it fixes what is surely a corrupted app database?

[Sonic3]

That will probably do it. And get it off the domain... although I prepped one of my images whilst joined. Worked ok.

 

 

EDIT: Download GeekUninstaller and see what it lists as installed apps - you can use this to remove provisioned apps as well as using get-appxpackage

 

Thanks. Trying this next...

[Sonic3]

That will probably do it. And get it off the domain... although I prepped one of my images whilst joined. Worked ok.

EDIT: Download GeekUninstaller and see what it lists as installed apps - you can use this to remove provisioned apps as well as using get-appxpackage

 

Unfortunately these didn't work either

I disjoined from the domain, deleted all local users/user profiles, added a new admin account, logged in as that one, deleted the other admin account, and I tried running GeekUninstaller but it doesn't show the offending store app/s. I guess that's because it's not showing the ones installed for other/all users?

 

Anyway, Sysprep failed again. Same error. Is there no hope? I'm about to give up and just start all over again, denying the PC access to the internet throughout the whole build.

 

Thanks to everyone for the suggestions so far anyway

[mikkydoos]

It's most likely not the internet @Sonic3, It'll be the users. I'd start again, don't join it to the domain, then you can't create any profiles that will burn you later. One local user only.

 

Snapshot it all the way too. After install, before logging in, before installing software etcn etc. Thats saved me loads of time.

[Sonic3]

It's most likely not the internet @Sonic3, It'll be the users. I'd start again, don't join it to the domain, then you can't create any profiles that will burn you later. One local user only.

 

Snapshot it all the way too. After install, before logging in, before installing software etcn etc. Thats saved me loads of time.

 

I've had an outside contractor come in and even he gave up trying to get Sysprep to run! Instead, he's taken the PC away to try and use something else to capture the image, hopefully avoiding the need to use Sysprep. It really does seem like the only solution for this is to not get into this situation in the first place (if you do intend to use Sysprep) by applying the preventative solutions suggested here and on the web. What a nightmare! But lesson learned.

 

Thanks everyone for all your help

[lukeacourt2]

Hi

 

I have looked into this about the Sysprep not woking and it is not working for me ither.

 

I did contact Microsoft's Support about this issue and they do admit it is a big problem with their OS Systems with Version Number 17763 only.

 

Microsoft said "They are Working on a Fix and it will be released with Windows 10 1903 May Update".

 

I hope i have answered this question for you.

 

Many Thanks

 

Luke A'Court

[gshaw]

Over the many years of Sysprep-ing, they seem to change things without really detailing what's changed. But, from experience I've found that you can't Sysprep a machine if it's joined on the Domain, and I leave all the Appx's as is and remove the ones I don't want as part of the MDT Sequence. Both of these caught me out a while back.

 

The only thing I'm doing to a captured image is purely windows updates and installing USBDLM. Everything is done on the MDT especially Office365 using Device Based Activation.

 

Just finalised our 1809 image so we have something ready, but waiting for 1903 now.

 

Pete

I go even further and don't do any form of capture at all. MDT deploys straight from the source WIM and everything else is packages as an Application

[Sonic3]

Hi

 

I have looked into this about the Sysprep not woking and it is not working for me ither.

 

I did contact Microsoft's Support about this issue and they do admit it is a big problem with their OS Systems with Version Number 17763 only.

 

Microsoft said "They are Working on a Fix and it will be released with Windows 10 1903 May Update".

 

I hope i have answered this question for you.

 

Many Thanks

 

Luke A'Court

 

 

In the end, I was able to sysprep 1809 by starting with a fresh install of Win 10 and keeping it off the internet as I installed programs etc. so I can confirm that's one solution that works! Of course, it might not matter much now 1903 has been released!