Jump to content




FazzaGBR

Image Capture Wizard Fails With Error Code (0x00004005)



Recommended Posts

I have created a new Windows 8.1update1 build in Hyper-V and installed all the software we need in the image, just like I have done numerous times before without any issues.

 

When I run the SCCM Image Capture Wizard it fails with error code 00004005 which after a quick search seems to be associated with the SysPrep part. Some websites list off a load of registry settings to reset which I have tried without any success as I just get the same error again. Another possible solution was to create a new local account with admin rights and try the wizard from that but alas the same error occurs.

 

I'm all out of ideas now so, help!

:(

post-25577-0-43935700-1441096910.png

Share this post


Link to post
Share on other sites


attach the smsts.log please...

Share this post


Link to post
Share on other sites

attach the smsts.log please...

 

I cant find one!

 

I've looked in c:\_SMSTaskSequence\ but there is no logs folder and the ccm folder doesnt exist in c:\windows

 

Is there anywhere else the log file might be?

 

*EDIT*

 

Found one!

 

It was in the C:\Users\IT Services\AppData\Local\Temp folder and I've not attached it to this post.

smsts.log

Share this post


Link to post
Share on other sites

Seems I have you all stumped!

 

I'm now preparing a Symantec Ghost image as I can no longer get SCCM to work which on 180 computers waiting for a new image is going to be fun and have to be done out of hours so no evenings for me for a while. :)

Share this post


Link to post
Share on other sites

look through the log file and search for the word 'failed'

 

you'll see a few issues highlighted below

 

<![LOG[Connection to "\\gonzo\deploy$\Images\STUDENT BUILDS\Golden Image V3 (With All ICT Serif Software)" failed with credential conflict. Using existing connection.]LOG]!><time="09:09:46.108-60" date="09-01-2015" component="OSDCaptureCD" context="" type="2" thread="1712" file="tsconnection.cpp:330">

 

and later on

 

<![LOG[sysprep did not complete successfully]LOG]!><time="09:18:02.430-60" date="09-01-2015" component="PrepareOS" context="" type="3" thread="1636" file="prepareos.cpp:514">
<![LOG[RunSysprep(sCmdLine, bActivate, m_bDebug), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1375)]LOG]!><time="09:18:02.430-60" date="09-01-2015" component="PrepareOS" context="" type="0" thread="1636" file="prepareos.cpp:1375">
<![LOG[unable to sysprep the machine, hr=80004005]

 

so... look next in

C:\Windows\System32\Sysprep\Panther

and the following files pointing to the failure:-

  • setupact.log
  • setuperr.log

can you attach them ?

Share this post


Link to post
Share on other sites

look through the log file and search for the word 'failed'

 

you'll see a few issues highlighted below

 

<![LOG[Connection to "\\gonzo\deploy$\Images\STUDENT BUILDS\Golden Image V3 (With All ICT Serif Software)" failed with credential conflict. Using existing connection.]LOG]!><time="09:09:46.108-60" date="09-01-2015" component="OSDCaptureCD" context="" type="2" thread="1712" file="tsconnection.cpp:330">

 

Thanks for the reply, I did see that and the credentials are correct. I even tried the actual domain administrator account rather then the sccmadmin one I have used in the past and still the same thing. The accounts connect to the sccm server OK with full admin rights to the shares.

 

I wasnt aware of the 2 log files that sysprep creates so thanks for that - I shall take a look and see what they say.

 

:)

 

I've uploaded one log file, but the other one is empty and as it's 0KB the forum wont let me upload it.

setupact.log

Share this post


Link to post
Share on other sites

This seems to be an issue with regards to using Hyper-V to create the image as I have used the same build-log tick sheet that I have and recreated the software build on a fresh VM and a physical machine and the Hyper-V VM fails with the same error code but the physical machine has created the image OK with the error.

 

The only issue with the physical machine method is that despite having Windows Updates turned off it automatically installs the Intel graphics card so before creating the image I have to make sure I uninstall it from Programs and Features - it's for things like this I have always used a VM in the past as nothing like this gets installed.

Share this post


Link to post
Share on other sites
To overcome this 3 Sysprep time limitaiton, following are the walkaround:

Open regedit and look for:


HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\CleanupState\

Set to value: 2


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

Set to value: 7


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion


\SoftwareProtectionPlatform\SkipRearm

Set to value: 1


Then, run the command:


msdtc -uninstall (wait a few seconds)

msdtc -install (wait a few seconds)


Then, reboot the system and try to run sysprep again.

It is working to me. Good luck to you.:)




Share this post


Link to post
Share on other sites

I also had this problem and did some research.

2016-10-10 12:48:33, Error SYSPRP Package Microsoft.FreshPaint_3.1.10156.0_x86__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

2016-10-10 12:48:33, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.

 

so what i did was uninstall the the Extra Cartoon apps. once i did that I reran the image file and started capturing the new image.

Share this post


Link to post
Share on other sites

Try running this PowerShell command for any users that've logged onto your reference PC:

 

Get-AppXPackage -User username | Remove-AppxPackage

 

This will remove windows store apps that're preventing sysprep from running

  • Like 1

Share this post


Link to post
Share on other sites

Same problem here, removed Sway, RemoteDesktop, and Eclipse app and the capture worked. Really wish MS would clean up stupid stuff like this.

Share this post


Link to post
Share on other sites

I think this happens when you click start before running sysprep. Something about clicking start in Windows 10 seems to trigger store app installs.

 

Also you can fix by creating a new local user, logging in as the new local user, delete local admin profile using control panel, log in as local admin (dont click start) delete new user profile and account, run capture media.

 

If you are customizing an image prior to capture (and sysprep) as local administrator etc, try doing so without clicking start, or dump the local administrator profile mentioned above. Seems kind of retarded, perhaps I should have been using Audit Mode, although I read the same issue happens in that scenario as well. Anyway, you will save a little HDD space by running sysprep from a newly created profile.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Adam Bise this saved the day for me, spent the better part of yesterday trying to get the Capture to run but kept getting sysprep failed, came in early today to have a fresh look at it and deleting the original profile I used to setup and configure W10, worked for me.

Share this post


Link to post
Share on other sites

Spoke too soon Sysprep goes through but get error 0x80220014 on the reboot, looks like a known issue with the version of ADK.

Share this post


Link to post
Share on other sites

In case it helps anyone else with this problem, I got this with a Gen 2 VM. Created a Gen 1 VM and it got past the error (still waiting for it to fully capture though...).In case it helps anyone else with this problem, I got this with a Gen 2 VM. Created a Gen 1 VM and it got past the error (still waiting for it to fully capture though...).

Share this post


Link to post
Share on other sites

Wow, I had an account for this site already that worked...

 

Since I have this problem constantly with Windows 10 and always get this forum on my searches.. here are my steps to resolve it.   (Other employees build their own images, so they constantly f-up the local admin account).

 

1.  Run the Powershell command  'Get-AppxPackage | Remove-AppxPackage'

2.  As someone stated above, configure your registry settings for SysPrep.

  1. Open regedit and look for:

  2. HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\CleanupState\ 
    Set to value: 2

  3. HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\ 
    Set to value: 7

  4. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SoftwareProtectionPlatform\SkipRearm 
    Set to value: 

  5. Then, run the command:

    msdtc -uninstall (wait a few seconds) 
    msdtc -install (wait a few seconds)

3.  From the Windows link above  (except my edits to make it work)

  1. Run the Import-Module Appx PowerShell cmdlet.
  2. Run Import-Module Dism.
  3. Run Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation.
  4. Delete whatever account is tied to all of your Appx packages.
  5. Reboot the computer and create a new local admin
  6. Reboot the computer and login to your new admin account.
  7. Capture the image as your new admin account.

 

Using these steps, I have been able to resolve all of my Windows 10 capture issues.  The final step where I capture with a clean admin account has worked every time.

 

 

 

Share this post


Link to post
Share on other sites

And update for 1709 capture.

 

Remove the following apps:

All games.

News

Paid WiFi Caller

Skype

Print 3D

Weather

XBox Live.

Share this post


Link to post
Share on other sites

Get-AppXPackage -Name Microsoft.SkypeApp | Remove-AppXPackage
Get-AppXPackage -Name 46928bounde.EclipseManager | Remove-AppXPackage
Get-AppXPackage -Name ActiproSoftwareLLC.562882FEEB491 | Remove-AppXPackage
Get-AppXPackage -Name AdobeSystemsIncorporated.AdobePhotoshopExpress | Remove-AppXPackage
Get-AppXPackage -Name Microsoft.BingNews | Remove-AppXPackage
Get-AppXPackage -Name Microsoft.NetworkSpeedTest | Remove-AppXPackage
Get-AppXPackage -Name Microsoft.Office.Sway | Remove-AppXPackage
Get-AppXPackage -Name Microsoft.RemoteDesktop | Remove-AppXPackage

Share this post


Link to post
Share on other sites

Just came across the same issue on a Win 10 Build 1709 PC, had to remove the following packages via PS, then SCCM image capture completed as expected

Get-AppXPackage -Name 46928bounde.EclipseManager | Remove-AppXPackage

Get-AppXPackage -Name Duolingo-LearnLanguagesforFree | Remove-AppXPackage

Get-AppXPackage -Name Microsoft.Office.Sway | Remove-AppXPackage

Get-AppXPackage -Name Microsoft.BingNews | Remove-AppXPackage

Get-AppXPackage -Name Microsoft.NetworkSpeedTest | Remove-AppXPackage

Get-AppXPackage -Name Microsoft.BingTranslator | Remove-AppXPackage

Get-AppXPackage -Name Microsoft.RemoteDesktop | Remove-AppXPackage

Share this post


Link to post
Share on other sites
On 5/8/2017 at 12:29 PM, Albane said:

Wow, I had an account for this site already that worked...

 

Since I have this problem constantly with Windows 10 and always get this forum on my searches.. here are my steps to resolve it.   (Other employees build their own images, so they constantly f-up the local admin account).

 

1.  Run the Powershell command  'Get-AppxPackage | Remove-AppxPackage'

2.  As someone stated above, configure your registry settings for SysPrep.

  1. Open regedit and look for:

  2. HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\CleanupState\ 
    Set to value: 2

  3. HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\ 
    Set to value: 7

  4. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SoftwareProtectionPlatform\SkipRearm 
    Set to value: 

  5. Then, run the command:

    msdtc -uninstall (wait a few seconds) 
    msdtc -install (wait a few seconds)

3.  From the Windows link above  (except my edits to make it work)

  1. Run the Import-Module Appx PowerShell cmdlet.
  2. Run Import-Module Dism.
  3. Run Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation.
  4. Delete whatever account is tied to all of your Appx packages.
  5. Reboot the computer and create a new local admin
  6. Reboot the computer and login to your new admin account.
  7. Capture the image as your new admin account.

 

Using these steps, I have been able to resolve all of my Windows 10 capture issues.  The final step where I capture with a clean admin account has worked every time.

The registry is missing the first entry, why would that be?

 

 

Share this post


Link to post
Share on other sites

I would like to add sth to this topic. Since version 1803 I wasn't able to delete the BuiltIn Administrator anymore, but it was needed by our CATIA Admins who built a script using the BuiltIn account.

So deleting the account that was bound to the apps preventing the WIM to be captured didn't work.

We use a VM to capture our WIMs so I checked the last DHCP lease, added a reservation for tha MAC and let our firewall admin block Internet-Access for this machine.

After doing that I enabled the BuiltIn Administrator, gave him a password and let the CATIA guys do their stuff.

Blocking access to the internet seems to prevent Windows from provisioning those nasty apps! The image could be captured without any problems.

If any problems occur with the image, I will let you know.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×