Windows 10 sysprep error.

John Johnson

@george1421 This is done in Windows PowerShell? I did remove the apps that way.

george1421

@John-Johnson Hmm the error message kind of indicates you ran
Remove-AppxProvisionedPackage this command which uninstalls the package but did not run this command Remove-AppxPackage to remove it from the current user. Again this is only a wild guess based on what I think the error messages means.

george1421

MS KB with this error listed (condition 3) https://support.microsoft.com/en-us/kb/2769827

John Johnson

@george1421 I ran the commands as Administrator. I did not run them under the original user account.

george1421

@John-Johnson Did you ever login as someone else on that system? If someone else has a profile that is already been created then you have your answer.

Again just guessing (at bit better each time) based on the info I have so far.

george1421

@george1421 I just found a comment about making sure your reference machine can’t connect to the internet, because if it can it will begin to download stuff.

I can so for my setup the reference machine can’t connect to the internet because we hare behind a firewall and proxy server. So the reference machine can not get out period.

Ref: http://deploymentresearch.com/Research/Post/450/Sysprep-broken-in-Windows-10-Build-9926

Workarounds posted

There are two workarounds:

1. Make sure the virtual machine you are using for reference images never connects to Internet.
2. Prior to run sysprep, have the task sequence delete all uppdated packages using PowerShell

To delete a package, use the following PowerShell command:

# Delete a package
Get-AppxPackage –Name *Insider* | Remove-AppxPackage

John Johnson

@george1421 The only reason for connecting to the internet is to run updates and get Adobe software, etc.

John Johnson

@george1421 I am going to start from scratch and see if I can work around this.

george1421

@John-Johnson Just as a recommendation, for windows updates use a 2012 wsus server. And for adobe updates download them to a flash drive so you can install them. It sounds like you are building your reference image manually using audit mode?

JJ Fullmer

@John-Johnson I ran into a similar error.
This answer is similar to the other’s but I had to run the following powershell script on every local user to get sysprep to work.

$AppsList = "Microsoft.Bing" , "Microsoft.BingFinance" , "Microsoft.BingMaps" , "Microsoft.BingNews"`
            , "Microsoft.BingSports" , "Microsoft.BingTravel" , "Microsoft.BingWeather" , "Microsoft.Camera"`
            , "microsoft.microsoftskydrive" , "Microsoft.Reader" , "microsoft.windowscommunicationsapps"`
            , "microsoft.windowsphotos" , "Microsoft.XboxLIVEGames" , "Microsoft.ZuneMusic"`
            , "Microsoft.ZuneVideo" , "Microsoft.Media.PlayReadyClient"

ForEach ($App in $AppsList)
{
    $PackageFullName = (Get-AppxPackage $App).PackageFullName
    if ((Get-AppxPackage $App).PackageFullName)
    {
        Write-Host "Removing Package: $App"
        remove-AppxProvisionedPackage -online -packagename $PackageFullName
        remove-AppxPackage -package $PackageFullName
    }
    else
    {
        Write-Host "Unable to find package: $App"
    }
}

See this post for more info
https://forums.fogproject.org/topic/5873/windows-10-unattend-xml-sysprep-answer-file-challenge/15

John Johnson

@george1421 I am actually building the image on the computer model we will use it on. We have several different models. I had no issues with Windows 7 but Windows 10 has been a struggle.

John Johnson

@Arrowhead-IT This actually worked for me!

John Johnson

@george1421 This worked. Arrowhead IT suggested the same.

george1421

@John-Johnson just for clarity the power shell script that ArrowHead-IT posted (same as what I posted only through the link) corrected your issue? You were able to update your win10 with all of the updates from the internet and you applied the adobe updates? I just want to ensure your workflow was the same and the only thing you changed was the powershell script.

John Johnson

@george1421 said in Windows 10 sysprep error.:

@John-Johnson just for clarity the power shell script that ArrowHead-IT posted (same as what I posted only through the link) corrected your issue? You were able to update your win10 with all of the updates from the internet and you applied the adobe updates? I just want to ensure your workflow was the same and the only thing you changed was the powershell script.

Yes. I was able to lift my image to fog by using powershell as the user and removing the offending apps.

John Johnson

I would say this topic is solved and I appreciate the support.

John Johnson

I apologize for not responding for a while. I did find a solution to this. I simply made an account that I knew I would remove later. I loaded everything I needed under that account. After I was finished I created the account I wanted to keep and removed the other. All the Microsoft apps went with it. This works for me and I hope it helps…

Quazz

I’d just like to mention that if you clean install the latest W10 iso, this shouldn’t happen (unless you incorrectly remove certain apps)

jscharfenberg

not sure if anyone has moved from this or not but there is a much easier way to sysprep then going through and removing the native apps. All I did was do a fresh install and have the OS offline. Go to services and disable Windows Update. Then go ahead and put it back online, install all my apps and use the SCCM 2012R2 capture ISO. Worked like a charm. It’s something in the Native App updates that kills sysprep.

davidedpg10

@jscharfenberg

I run this on powershell

Get-AppxPackage -AllUsers | Remove-AppxPackage

And then I use this sysprep unattend file. It works really well in my environment.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">

<!-- Autounattend_x64_BIOS_sample.xml

This file automates the Windows installation.

    Before using this file:
     * Replace ProductKey with a product key for the edition of Windows you are installing
       (example: Windows 8 Pro)
       Note:
          The product key used in Microsoft-Windows-Setup\UserData\ProductKey\Key 
          can be used many times in different installations and is not used to activate Windows. 
          It is only used to choose which edition of Windows to install. 
          
          The individual product key is either specified by the user, or by setting 
          Microsoft-Windows-Shell-Setup\ProductKey.
    * Set the default language to your own:
      Replace "en-US" with your language code in Microsoft-Windows-International-Core-WinPE\SetupUILanguage. 
      For a list of languages, see http://go.microsoft.com/fwlink/?LinkId=206620.
    * OEMs: Replace OEMInformation with your support information

    To use this file: 
       Save this file on the root of a USB flash drive with the filename: Autounattend.xml
       Put the Windows DVD and the USB key into a new x64-BIOS PC.
-->


   <settings pass="specialize">
       <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <CopyProfile>true</CopyProfile>
       </component>
   </settings>
   <settings pass="windowsPE">
       <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
           <SetupUILanguage>
               <UILanguage>en-US</UILanguage>
           </SetupUILanguage>
           <InputLocale>en-US</InputLocale>
           <SystemLocale>en-US</SystemLocale>
           <UILanguage>en-US</UILanguage>
           <UserLocale>en-US</UserLocale>
       </component>
       <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
           <UserData>
               <AcceptEula>true</AcceptEula>
           </UserData>
       </component>
   </settings>
<settings pass="oobeSystem">
 <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <OOBE>
   <HideEULAPage>true</HideEULAPage>
   <HideLocalAccountScreen>true</HideLocalAccountScreen>
   <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
   <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
   <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
   <SkipUserOOBE>true</SkipUserOOBE>
   <SkipMachineOOBE>true</SkipMachineOOBE>
  </OOBE>
 </component>
</settings>
</unattend>

Windows 10 sysprep error.

187

11.6k

17.1k

154.6k