Highlighted
AMDarren
1 Copper

Sysprep Error after upgrade from 1803 to 1809

Jump to solution

I have maintained three versions of an image in the past. One for standard desktops, one for our graphics team, and one for our engineers. The graphics and engineers were built by adding additional software/configs to the standard image.

 

We have a PC dedicated for building images, running Windows 10 as the host for VMWare Workstation v14 and we build the virtual images within VMWare.

 

In the past, I have been able to upgrade my images to the next build, without having to do a clean install. This has worked fine, up until 1809 and this was AFTER 1809 was updated by Microsoft, not to cause the problem with deleting local document files.

 

Back when we started doing this, I first clean installed I believe build 1709 as the standard image, with one administrator login.

 

I followed online guides that explained that prior to plugging it into the LAN to go online, to turn off the windows store updates by running the following, which worked well for me:

reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsStore /v AutoDownload /t REG_DWORD /d 00000002 /f

reg add HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent /v DisableWindowsConsumerFeatures /t REG_DWORD /d 00000001 /f

reg add HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\ContentDeliveryManager /v SilentInstalledAppsEnabled /t REG_DWORD /d 00000000 /f

 

I then ran windows updates, added my other software configurations, then ran windows update again, ran disk cleanup, and made tweaks to the Microsoft settings and tools, etc.

 

One of the last steps is to create a new administrator login account, then we login with that second administrator account, then use DefProf (https://www.forensit.com/support-downloads.html) to copy the original administrator profile, to the default user profile. This way, the Start menu settings that we created, etc, are all copied to new users, for new machines from Dell, even before any global policies are applied after login to the domain. Before we sysprep, we log back into the original administrator account, and then delete the second temp admin account, also removing the files from the account. Then we run disk cleanup again and remove any existing system restores, and we create a new one. So that second temp admin account should be GONE!?

 

We have been using Dell Image Assist, which preps things for Dell machines - and before I would run that, I would disconnect the host machine from the network (and thus the images machines), then I'd clone the source image that I built. And then on the clone, I would change the first key above back to Decimal 4, and I would delete the other two (DisableWindowsConsumerFeatures & SilentInstalledAppsEngine).

 

The last thing Dell Image Assist does, is run Microsoft SysPrep.

 

For my upgrade from 1803 to 1809, I could not get this upgrade to work. I tried many different things.

 

First, Windows Update did not detect/download the 1809 update, even though I have Windows Update configured to receive Semi-Annual Channel (Targeted) updates.

 

So I went to https://www.microsoft.com/en-gb/software-download/windows10 and attempted to "Update Now". I noticed the updates would get to certain percentages ie 71% or something (I don't remember the exact number) but then return to 0% then continue back up. It was bizarre. After 20 minutes or so, the updater fails with an error 0x80070522, which means the update was being performed without an Administrator account. But I WAS using an Administrator account. On three different machines I tried it on!

 

Next, I logged into our Microsoft Volume License Center and downloaded the most current 1809 ISO file and then used rufus to burn it to a bootable USB drive. Then I attempted to run the Windows Installer USB drive against the Windows 1803 image I was trying to upgrade to 1809 and then SysPrep. The Windows Installer 1809 USB was able to complete the update on the 1803 to 1809 image I was creating. And I confirmed 1809 was installed by checking the About page.

 

Then I followed my steps to clone my 1809 image, disconnect it from the LAN, change the registry, then run Dell Image Assist/Sysprep. But then I started to get the all-too-familiar Sysprep issues with packages that were updated/installed in a manner which clobbers sysprep.

 

The first set of errors I received, are below:

 

 

*** SYSPREP TRY NUMBER 1 ***

 

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP Package Microsoft.BingWeather_4.22.3254.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

 

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

 

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

 

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

1/9/2019 3:24:04 PM:

1/9/2019 3:24:04 PM: Checking if file exists: C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2

1/9/2019 3:24:04 PM: Checking if file exists: C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2

1/9/2019 3:24:04 PM:

1/9/2019 3:24:04 PM: C:\WINDOWS\System32\Sysprep\Panther\setuperrHOLD.log exists.

1/9/2019 3:24:04 PM: ----------------------------------

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP Package Microsoft.BingWeather_4.22.3254.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

1/9/2019 3:24:04 PM:

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

1/9/2019 3:24:04 PM:

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

1/9/2019 3:24:04 PM:

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2

1/9/2019 3:24:04 PM: 2019-01-09 15:18:14, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

1/9/2019 3:24:04 PM:

1/9/2019 3:24:04 PM: ----------------------------------

1/9/2019 3:24:04 PM: Sysprep = FAILED

1/9/2019 3:24:04 PM: ----------------------------------

1/9/2019 3:24:04 PM: Copying C:\WINDOWS\Panther\setup.etl

1/9/2019 3:24:04 PM: sysprep.exe /generalize /oobe /quit /unattend:C:\WINDOWS\Panther\Unattend.xml Failed.

1/9/2019 3:24:04 PM: Error Code: 0

1/9/2019 3:24:04 PM: Please contact Microsoft for this error. Otherwise please restore an earlier version of this image and try again to run through the tools. Auto Capture Error: 201

1/9/2019 3:24:04 PM: C:\WINDOWS\System32\Sysprep\Panther\setuperr.log exists.

1/9/2019 3:24:04 PM: Please read that file for more detail."C:\WINDOWS\Panther\DTRI\LOGS\Auto_Capture_Prep_Tool.log"

1/9/2019 3:30:35 PM: Running Clean up Scripts... Please Wait...

1/9/2019 3:30:35 PM: dism.exe QUERY for: " /Cleanup-Wim"

1/9/2019 3:30:36 PM: exitcode2 = 0

1/9/2019 3:30:36 PM: Running Clean up Scripts... Complete

 

 

After the above, I tried running these commands in an elevated PowerShell window, on the 1809 image:

 

Get-Appxpackage -allusers | where {$_.name -like "*Microsoft.BingWeather*"} | Remove-Appxpackage

Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Microsoft.BingWeather*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}

Remove-AppPackage -AllUsers -Package "Microsoft.BingWeather_4.22.3254.0_x64__8wekyb3d8bbwe"

 

Then I tried Sysrep again. Sysprep then didn't produce an error for the Microsoft.BingWeather, but then as I expected, it moved on to yet another package issue. I kept trying the above for each errored package and began to lose track of all the resolutions I attempted on the Packages, such as below:

 

Get-Appxpackage -allusers | where {$_.name -like "*Microsoft.DesktopAppInstaller*"} | Remove-Appxpackage

Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Microsoft.DesktopAppInstaller*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}

Remove-AppPackage -AllUsers -Package "Microsoft.DesktopAppInstaller_1.0.12271.0_x64__8wekyb3d8bbwe"

 

Sysprep continued to produce errors for other packages then stopped. I was so frustrated. I wasn't sure how many of these I'd have to go through and how much time I'd be wasting, so I gave up on that idea.

 

I decided to go back to my original working 1803 image source that I used just before running Dell Image Assist/Sysprep. I kept the host disconnected, then ran the Windows 1809 Installer USB against a [semi-clean] 1803 image that I had last perfected. That ran fine.

 

I never plugged the host back in, and then moved onto Dell Image Assist/Sysprep on my updated 1803 > 1809 image.

 

But, as I thought, I started to get the Microsoft.BingWeather errors again.

 

I thought - how is this possible - when I had a working 1803 image - and even though my 1803 image already had the Windows Store updates disabled - I also had the computer disconnected from the Internet - and ran just the Windows 1809 Installer directly against my working 1803 image?

 

I assume these Microsoft Store packages were updated by the Windows 1809 Installer somehow, and the 1809 Installer itself, clobbered the working 1803 image. It's just unfriggen believable.

 

The following is the Sysprep output after my 1803 > 1809 upgrade using my disconnected machine and just the Windows 1809 Installer. I'm not even sure if it's the exact same errors as above.

 

 

*** SYSPREP TRY - POST 1803 to 1809 WIN INSTALLER UPGRADE ***

 

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP Package Microsoft.BingWeather_4.22.3254.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

 

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

 

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

 

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

1/11/2019 11:46:03 AM:

1/11/2019 11:46:03 AM: Checking if file exists: C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2

1/11/2019 11:46:03 AM: Checking if file exists: C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2

1/11/2019 11:46:03 AM:

1/11/2019 11:46:03 AM: C:\WINDOWS\System32\Sysprep\Panther\setuperrHOLD.log exists.

1/11/2019 11:46:03 AM: ----------------------------------

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP Package Microsoft.BingWeather_4.22.3254.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

1/11/2019 11:46:03 AM:

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

1/11/2019 11:46:03 AM:

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

1/11/2019 11:46:03 AM:

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2

1/11/2019 11:46:03 AM: 2019-01-11 11:44:06, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

1/11/2019 11:46:03 AM:

1/11/2019 11:46:03 AM: ----------------------------------

1/11/2019 11:46:03 AM: Sysprep = FAILED

1/11/2019 11:46:03 AM: ----------------------------------

1/11/2019 11:46:03 AM: Copying C:\WINDOWS\Panther\setup.etl

1/11/2019 11:46:03 AM: sysprep.exe /generalize /oobe /quit /unattend:C:\WINDOWS\Panther\Unattend.xml Failed.

1/11/2019 11:46:03 AM: Error Code: 0

1/11/2019 11:46:03 AM: Please contact Microsoft for this error. Otherwise please restore an earlier version of this image and try again to run through the tools. Auto Capture Error: 201

1/11/2019 11:46:03 AM: C:\WINDOWS\System32\Sysprep\Panther\setuperr.log exists.

1/11/2019 11:46:03 AM: Please read that file for more detail."C:\WINDOWS\Panther\DTRI\LOGS\Auto_Capture_Prep_Tool.log"

1/11/2019 11:46:05 AM: Running Clean up Scripts... Please Wait...

1/11/2019 11:46:05 AM: dism.exe QUERY for: " /Cleanup-Wim"

1/11/2019 11:46:06 AM: exitcode2 = 0

1/11/2019 11:46:06 AM: Running Clean up Scripts... Complete

1/11/2019 11:46:06 AM:

1/11/2019 11:46:06 AM: --------------------------------------------------------------------

1/11/2019 11:46:06 AM: --------------------------------------------------------------------

1/11/2019 11:46:06 AM: Finished - Auto_Capture_Prep_Tool VERSION: 5.6.0.5 Time: 1/11/2019 11:46:06 AM

 

 

I have tried some other "potential" solutions to the package issues. Some of them I do not understand so I have not tried. Those I've tried include the above AppxPackage type commands, and I've also tried creating yet another second new administrator account, then running Image Assist/Sysprep on that second account, but that had no effect to fix the above.

 

At one point I also tried going into [HKEY_LOCAL_MACHINE\SYSTEM\Setup] and deleting the entry called "Upgrade" and any entries that started with "Uninstall". Then deleting the entire key [HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade]. Then deleting the entire key (or keys if there is more than 1) [HKEY_LOCAL_MACHINE\SYSTEM\Setup\Source OS]. Then rebooting. That had no effect.

 

I also tried... after the cleanup of AppX garbage, setting the status:

HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\

CleanupState:2

HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\

GeneralizationState:7

The above had no effect.

 

I saw there is an update to AppxDBEditor for 1809 (by a '-Steve-' on this board, but I'm not sure how to reach him, or if it would fix these issues.

 

I can't tell you how much time I've wasted on this. It is extremely annoying! Microsoft should have the ability to build a Sysprep that gets rid of these issues during the Sysprep process!

 

Does anyone have a solution for this? Please share with us!

 

Now before you tell me "you always have to use a clean image" for each build update, that is NOT what Microsoft's own documentation tells you. See: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/sysprep--system-preparation--o... - specifically: "Beginning with Windows 10, version 1607, Sysprep can be used to prepare an image that has been upgraded."

 

Thanks for reading.

 

Darren Nye

3 Replies
PDKcarney
1 Copper

Re: Sysprep Error after upgrade from 1803 to 1809

Jump to solution

I'm experiencing the exact same issue and have tried everything in the link below.  Still no luck.

https://social.technet.microsoft.com/Forums/en-US/07de4b3f-b1f0-4205-9e1a-6be52d41b8ca/sysprep-with-...

0 Kudos
Moderator
Moderator

Re: Sysprep Error after upgrade from 1803 to 1809

Jump to solution
0 Kudos
Moderator
Moderator

Re: Sysprep Error after upgrade from 1803 to 1809

Jump to solution

*UPDATE FIXED*

Yesterday Microsoft released KB4476976 which after applying and rebooting resolves the Sysprep issue seen after cleaning up the previous version of Windows.

 

 

Tyler

0 Kudos