Deploy Windows 10 In-Place Upgrade Using Configuration Manager in Just 2 Steps

*****Update 2017/02/01 – You no longer need to download the ZIP file to import the SCCM task sequence for the upgrade to Windows 10. It is now an available task sequence in the current branch build of Configuration Manager.


Yes, only two steps!

Now that Windows 10 is available, I want to demonstrate how easy it is to deploy using System Center Configuration Manager. If you’ve previously deployed Windows 7/8 upgrades using SCCM, Windows 10 is an entirely different ballgame. The biggest difference is that in-place upgrades are now an option. You no longer have to worry about USMT customization, application migration, or other complicated configuration- it just upgrades in-place and keeps everything. If you’ve done Windows OS migrations in the past, you know this saves a ton of work. You can still do  deployments using the same methods used before, but this is just an easier way to upgrade current systems.

Note that you must be running SCCM 2012 R2 SP1 or SCCM 2012 SP2 to use this feature. Check out an earlier article I posted for guidance on this upgrade.

Step 1: Import the Windows 10 Upgrade task sequence and media

Grab the Windows 10 Upgrade task sequence from this TechNet blog article by Aaron Czechowski. The files are in a zip file at the bottom of the page. Extract the zip file to a directory that is suitable to serve as the location for the package source before you import them (this location is easy to change later if you need to). After the zip file is extracted, copy your Windows 10 Enterprise media into the folder named “…\Windows10Upgrade2012R2SP1\Windows vNext Upgrade_files\Windows vNext Upgrade Media“. This includes all of the files and folders from the root of the Win10 ISO, so it should look like this:

5

Import Windows vNext Upgrade.zip into SCCM by going to the Software Library, right-clicking Task Sequences under Operating Systems, and choosing Import Task Sequence.

1

This new task sequence will also create a couple new packages required for deployment. Be sure to copy these out to all applicable distribution points after the wizard.

3

You can view the imported task sequence now in the console, but no changes are required.

6

Step 2: Deploy the task sequence to your systems

This task sequence does not use any boot images, OS Installers/Images, or any other content normally required for OS deployment – just the two packages created during the import process.

Deploy this task sequence the same way that you would do any other deployment. In this test, I’ll be creating an optional deployment to a Windows 8.1 Enterprise system. Of course, you have the option to schedule the deployment, give it a deadline, and choose to make it optional or required.

7

Once the targeted SCCM client checks in and finds the new deployment (also depending on what options you used during configuration), it will now be available to install.

8

Once you choose Install, no more user input should be required.

Screen Shot 2015-07-30 at 1.34.58 PM

And we’re off.

Screen Shot 2015-07-30 at 1.43.02 PM

Wasn’t that easy? When installation completes, everything should still be in place (applications, profiles, settings, etc) and you should be able to log onto the domain like usual.

Thanks for reading! Leave a comment if I can answer any questions.

115 thoughts on “Deploy Windows 10 In-Place Upgrade Using Configuration Manager in Just 2 Steps”

  1. Hi There,

    When I try to install the task sequence I receive the following error message:

    Task Sequence: Windows vNext Upgrade has failed with the error code (0x80004005). For more information, contact your system administrator or helpdesk operator.

    Can you confirm what logs I may need to check to resolve this?

    Thanks

    Chris

    1. Hey Chris,

      That’s a very generic error. Can you find the SMSTS.log file and share it? DId you copy all package content to your distribution point?

      Thanks,

      Josh

    2. Hello,
      Solucion for error 0x80004005
      Add user in local group Administrators and if you deploy / upgrade in virtual machine Hyper-V use 3000mb memory.

      1. HI Ricardo, i got a problem with the same error but into smst.log show me that:

        Windows Setup failed with hexadecimal exit code 0xC1900204 (decimal 3247440388). To identify the type of issue, lookup it against the table of known values of Windows Setup errors online.

        Failing this task sequence step upgradewindows.cpp: 739

        1. Just some brief research on that error seems to indicate some problems with the existing installation… try running “sfc /scannow” on your system or an image repair (“DISM.exe /Online /Cleanup-image /Restorehealth” if Win8 or later, System Update Readiness Tool if Win7 or earlier).

          1. Thank you for your help. I downloaded image for the microsoft porta and these image i´m deploying with sccm. do i need to make any change over the image?

  2. Great guide, worked like a charm!
    But, I got additional steps in the post-prosessing stage (additional software, drivers, updates), where the computer stays in the logon-screen, ready to log on, and the task sequence runs in the background – hidden. This will be a problem for the users who think their computer is finished, when it’s still running.

    My question is, is there a way to make the background-task sequence visible till all the steps are done?

    1. If the task sequence is still running steps, it will not sit at the logon screen. I’d check your TS log file – it sounds like maybe those steps aren’t running.

  3. Hey. Great guide. I am trying to deploy this to a select set of test machines. I’ve followed all the steps to a tee – I have even went back through the TechNet article, and I cannot get this to properly deploy.

    We’ve recently upgraded SCCM from R2 to R2 SP1 and upgraded the clients to the latest versions as well. I added the computers into the Device Collection, I’ve made sure the content has updated to the DP, I’ve deployed and ran manual machine policy checks on the client and the deployment simply doesn’t display. I know the client is working because other deployments to that same machine have displayed and ran immediately. What am I missing?

    1. Update: Not sure if it’s relevant or not, but on the Config Mgr Properties on the client machine on the Components tab, Operating System Deployment Component says “Installed” instead of “Enabled”.

      1. Brad,

        Sorry for just getting to this. It sounds like you’re not able to get the Windows 10 task sequence to run at all? Does the task sequence show in the Software Center for clients and did you make it available in the Software Center? Did you try creating a new collection, adding the desired clients to that collection, and then deploying to that specific collection instead? What does the deployment status for the clients say under the monitoring section? Are you sure that clients have been upgraded to the latest version, including the cumulative update? What version number are your targeted SCCM clients at?

  4. Would this work with a Windows 10 Pro installation created by the free upgrade tool for machines running Win7 and Win8 pro? Would be a great way to get your free Win10 upgrade, rather than having to do this on your individual machines.

    1. This should work for Pro editions as long as the version and architecture matches your previous installation. I don’t believe this solution will be able to take advantage of the free upgrade, though, unless you know the product key from your free upgrade and then specify in this process.

  5. This worked great on test unit #1! Thanks!

    One further step I’d like to take is having Windows 10 automatically activated.
    Has anyone attempted to do this?

    1. Matt,

      You can do this by editing the command line in the “Upgrade Windows” step in the task sequence. If you add the switch that specifies a Windows 10 key, it will automatically activate, as well. The switch to do that is: /pkey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

  6. Hey Josh,
    I saw some people mention this in Aaron’s post also, but I have not found a fix yet. The PreSetup.ps1 script sets ccmexec and smstsmgr startup type to disabled. In my environment those service never get set back to automatic and manual so after the upgrade step finishes none of the Post Processing steps occur. I did change line 66 of the SetupComplete.ps1 script as someone suggested in Aaron’s post, but that did not work for me. Let me know if you have any idea’s, I’m running out of things to try.

    Thanks you!

    1. I may have found it. My upgrade windows step was missing the setupcomplete.cmd from /PostOobe %SystemDrive%\_vNextUpgrade\

      I’m testing now.

        1. Nope, didn’t work. I’m going to try running the setup\upgrade outside of ConfigMan to see if it obeys the /PostOobe command. Any ideas would be greatly appreciated.

          Thanks

          1. Found the issue. We have the Altiris Dagent on our desktops for some legacy apps that have not been moved to SCCM yet. The Dagent was blocking the SetupComplete.cmd file from running. I disabled the service in the PreSetup.ps1 and everything worked. I read where some AV software can do this also.

  7. I cant seem to get the inplace upgrade from win 8.1 ent eval to win 10 ent? I cant get win 7 pro an win 8.1 pro to win 10 pro, but not the Ent inplace upgrades?

    thanks Mike

    1. Mike,

      Unfortunately, I don’t think the evaluation version will work when upgrading. I had the same problem. You may need to license Windows 8.1 Enterprise before trying the upgrade.

  8. I tried a licensed version of win 7 enterprise and it is failing?It downloads the scripts & OS media, then hangs for an hour and dies?
    any help is greatly appreciated!
    some errors:

    This operation returned because the timeout period expired. (Error: 000005B4; Source: Windows)]LOG]!>

    Operation aborted (Error: 80004004; Source: Windows)]LOG]!>

    1. more errors

      This operation returned because the timeout period expired. (Error: 000005B4; Source: Windows)]LOG]!>

      Operation aborted (Error: 80004004; Source: Windows)]LOG]!>

      thanks

      1. Hey Mike,

        I think we need to dig deeper into the logs to resolve this. It’s interesting that it hangs for so long before failing. If you run the Windows 10 in-place upgrade manually (straight from the same media without using SCCM), does it succeed or fail? What does the error say? I’d start there.

  9. Everything works well, consitantly but in each case the C:\_SMSTaskSequence folder is left behind.
    Its empty and doesn’t take up any space but it would be nice to have it removed.

    Is yours getting removed; any ideas for me?

    PS this does work when I run it manually cmd /c rmdir /s /q %SystemDrive%\_vNextUpgrade

    may be it just needs a delay?

    1. If the folder is empty, then the task sequence is doing its job and completed successfully. If there are items inside of it, then it didn’t complete. You could definitely add that command line step at the end of your task sequence to delete that directory. It might be easiest just target all Windows 10 systems to run that command as a deployment.

  10. HI Josh,

    Great Vid and awesome guide. However, I am failing 100% of the time during the “UPGRADE WINDOWS” TS step. I get the following ERRORS:
    “Failed to run the action: PreSetup.
    Incorrect function. (Error: 00000001; Source: Windows)”

    “Failed to run the action: Upgrade Windows.
    Unknown error (Error: C1900208; Source: Unknown)”

    I am trying to upgrade from WIn 7 PRO to WIN 10 ENT.

    1. Dimitri,

      What happens if you just run the Windows 10 upgrade straight from the media, instead of using the task sequence? If you run it on the same system, you should get an error that details why the process failed. Give that a shot and let us know what you find.

      1. You can’t upgrade from WIN 7 PRO to WIN 10 ENT. The upgrade has to be 7 PRO to 10 PRO or 7 ENT to 10 ENT. Hope this helps.

        1. Once you upgrade from Win 7 Pro to Win 10 Pro, you can change the license type to Win 10 Ent, if you have the volume licensing infrastructure.

  11. Hi
    When SEP installed on windows 7/8/8.1, task give me error. after uninstall SEP i can be upgrade to Windows 10.
    I want to run scripts and install SEP , while or after upgrade in same SCCM task. how can i do it?

    1. Mehmet,

      Your best bet may be to script the uninstallation of the SEP client into the task sequence. You can always reinstall it at the end.

  12. Hi, Thanks for such nice blog and it worked for me :-)

    But in the media package i have copied 64 bit media and i got some machines with 32 bit installed and i want to perform in place upgrade for those machine to 32 bit windows 10,

    Could i create another package for 32 bit media with same vnext file or i have to first uninstall the 64 package and then do i import for 32 bit.

    please help me out

  13. Hi,

    the first time i imported the task sequnce successfully after i delete it and try again to import it i got an error,

    xml error and failed to import it, any help.

    1. just remember to also delete the two packages, not only the Task sequence. When all 3 are deleted and you try to import it again it should worl

  14. Hey. I followed you instructions to a T. Works great. Unfortunately, while Windows 10 is installing, it always fails out at about 70% into it and reverts back to Win 8.1. To see if there was something wrong with the source of Windows 10, I installed it manually using the same source SCCM is using and it installs perfectly fine. When I deploy the task sequence to my test machine, again, it fails at around 70%. Any logs that I should be looking at? I’ve tried a few, but nothing is really hinting at why this would fail at around that percentage. All help is much appreciated.

  15. Great article, Thanks Josh!

    I’ve been testing in lab with a Hand full of Clients (both Windows 7 and 8). I have always the same issue:
    Upgrade stuck at 100% and after timeout rollback takes place.
    after analyzing the SetupComplete.log on all machines is the last entry “Wait for Task Manager Service…”

    I don’t know if it has anything to do with what Aaron Czechowski mentiones here:
    https://social.technet.microsoft.com/Forums/en-US/da4a94f1-b561-4482-8cfe-31ea0aa0fc13/windows-7-to-windows-10-technical-preview-9926-vnext-inplace-upgrade-task-sequence-sccm-2012-r2?forum=WinPreview2014Setup
    Do you have any Idea?

  16. Hello this was a great post. I was able to upgrade desired machines to windows 10 64bit. I work in a mixed environment and wanted to deploy both 32 and 64 bit upgrades. Is that possible or will have to delete the 64bit one i have set up and recreate the packages in 32bit?

    1. Hi Rey,

      That’s fine you don’t have to delete the previously created package all you have to do is once you create the package for 64 bit change the TS name and then create another TS for 32 bit machines using the same method:-)

      1. When I try to import the new TS Configuration Manager already sees the previous packages and it does not let me proceed. I have the option to overwrite the packages but that would erase my 64bit package at least the media package.

        1. Do one thing, Right click on the the TS you would have imported the TS and copy it, Once that will be copied right click on the copied task sequence and change the name of it and then remove all the refence package as this will be the copy of ts you would have imported so dowload the ts and then extract it to a unc path the provide the path to the copied ts and finally copy your win 10 image to media package and provide the path.

          1. Got it thank you. I copied the TS. I Created a new standard package with the 32bit install files with the option not to create the program. Went back to my new TS and edited it and changed the package for the media to the new package created. Thank you for your help.

  17. Hi,
    Im wondering is there a way to keep the keyboard settings as my deployment changes the keyboard settings to US eng and i need it to stay at irish eng

  18. Thanks for publishing this guide!

    I was able to start the upgrade through Software Center but it is failing at the “Upgrade Windows” step when it tries to execute the command with setup.exe. The error from the smsts.log is as follows:

    Working dir ‘C:\_SMSTaskSequence\Packages\CA500B5B’ InstallSoftware 2/9/2016 2:58:48 PM 7676 (0x1DFC)
    Executing command line: Run command line InstallSoftware 2/9/2016 2:58:48 PM 7676 (0x1DFC)
    Process completed with exit code 2147942405 InstallSoftware 2/9/2016 3:04:14 PM 7676 (0x1DFC)
    Command line returned 2147942405 InstallSoftware 2/9/2016 3:04:14 PM 7676 (0x1DFC)
    Process completed with exit code 2147942405 TSManager 2/9/2016 3:04:14 PM 1616 (0x0650)
    !——————————————————————————————–! TSManager 2/9/2016 3:04:14 PM 1616 (0x0650)
    Failed to run the action: Upgrade Windows. Permissions on the requested may be configured incorrectly.
    Access is denied. (Error: 80070005; Source: Windows) TSManager 2/9/2016 3:04:14 PM 1616 (0x0650)

    I know it says access is denied but what is it referring to that it cannot get access to? Afterwards I checked the C:\_SMSTaskSequence folder and it is empty.

  19. Josh awesome tutorial thank everything was great until i tried to deploy. I deployed it showed in Software Center and i attempted to install but then failed with:

    Task Sequence: Windows vNext Upgrade has failed with the error code (0x80004005). For more information, contact your system administrator or helpdesk operator.

    I can’t get this to work for the life of me.

    my smsts log can you help me ????

    ==========[ TsProgressUI started in process 4236 ]========== TsProgressUI 4208 (0x1070) 2/17/2016 11:38:17 AM
    Registering COM classes TsProgressUI 4208 (0x1070) 2/17/2016 11:38:17 AM
    sbModulePath = C:\Windows\CCM\TsProgressUI.exe TsProgressUI 4208 (0x1070) 2/17/2016 11:38:17 AM
    Shutdown complete. TsProgressUI 4208 (0x1070) 2/17/2016 11:38:17 AM
    Successfully intialized Logging for TS Manager. TSManager 4268 (0x10AC) 2/17/2016 11:38:33 AM
    Commandline: C:\Windows\CCM\TSManager.exe /service TSManager 4268 (0x10AC) 2/17/2016 11:38:33 AM
    Successfully registered Task Sequencing COM Interface. TSManager 4268 (0x10AC) 2/17/2016 11:38:33 AM
    Executing as a service TSManager 4268 (0x10AC) 2/17/2016 11:38:33 AM
    Started ServiceMain TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Task Sequence Manager executing as service main thread TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Reading logging settings from TS environment to set TS logging TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca … TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Waiting for CcmExec service to be fully operational TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    CcmExec service is up and fully operational TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Remediating TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Error getting system isolation info. Code 8027000C TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Remediation failed. Code 8027000C TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Remediation failed with error code 8027000C TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Parsing task sequence . . . TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Task sequence schema version is 3.00 TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Current supported schema version is 3.10 and 3.00 TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Starting Task Sequence Engine . . . TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    **************************************************************************** TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Set a global environment variable _SMSTSNextInstructionPointer=0 TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Set a global environment variable _SMSTSInstructionTableSize=16 TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Set a global environment variable SMSTSRebootRequested= TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Set a global environment variable SMSTSRebootDelay= TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Set a global environment variable SMSTSRebootMessage= TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Set a global environment variable SMSTSRebootReason= TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Set a global environment variable SMSTSRetryRequested= TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    The task execution engine started execution TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Set authenticator in transport TSManager 4300 (0x10CC) 2/17/2016 11:38:33 AM
    Start executing an instruction. Instruction name: Preparation. Instruction pointer: 0 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a global environment variable _SMSTSCurrentActionName=Preparation TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a global environment variable _SMSTSNextInstructionPointer=0 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    The group (Preparation) has been successfully started TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set authenticator in transport TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Updated security on object C:\_SMSTaskSequence. TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a global environment variable _SMSTSNextInstructionPointer=1 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a TS execution environment variable _SMSTSNextInstructionPointer=1 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a global environment variable _SMSTSInstructionStackString=0 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a TS execution environment variable _SMSTSInstructionStackString=0 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Save the current environment block TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a global environment variable _SMSTSLastActionRetryCount=0 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Start executing an instruction. Instruction name: Check Readiness. Instruction pointer: 1 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a global environment variable _SMSTSCurrentActionName=Check Readiness TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a global environment variable _SMSTSNextInstructionPointer=1 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a local default variable OSDCheckFreeDiskSpace TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a local default variable OSDCheckMemory TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a local default variable OSDCheckOSType TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a local default variable OSDCheckProcessorSpeed TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a local default variable OSDFreeDiskSpace TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a local default variable OSDMemory TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a local default variable OSDOSType TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a local default variable OSDProcessorSpeed TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a global environment variable _SMSTSLogPath=C:\Windows\CCM\Logs\SMSTSLog TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Expand a string: OSDPrestartCheck.exe TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Expand a string: TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Start executing the command line: OSDPrestartCheck.exe TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    !——————————————————————————————–! TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Expand a string: WinPEandFullOS TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Executing command line: OSDPrestartCheck.exe TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    ========================= [ osdprestartcheck.exe ] ========================= CheckReadiness 5344 (0x14E0) 2/17/2016 11:38:34 AM
    Command line: ‘”OSDPrestartCheck.exe”‘ CheckReadiness 5344 (0x14E0) 2/17/2016 11:38:34 AM
    Checking memory.. CheckReadiness 5344 (0x14E0) 2/17/2016 11:38:34 AM
    nFoundMemory >= nRequiredMemory, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prestartcheck\osdprestartcheck.cpp,60) CheckReadiness 5344 (0x14E0) 2/17/2016 11:38:34 AM
    Memory requirement validation failed. (Required: 2048 MB, Found: 1936 MB) CheckReadiness 5344 (0x14E0) 2/17/2016 11:38:34 AM
    Process completed with exit code 2147500037 TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    !——————————————————————————————–! TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Failed to run the action: Check Readiness.
    Unspecified error (Error: 80004005; Source: Windows) TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set authenticator in transport TSManager 4300 (0x10CC) 2/17/2016 11:38:34 AM
    Set a global environment variable _SMSTSLastActionRetCode=-2147467259 TSManager 4300 (0x10CC) 2/17/2016 11:38:35 AM
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 4300 (0x10CC) 2/17/2016 11:38:35 AM
    Clear local default environment TSManager 4300 (0x10CC) 2/17/2016 11:38:35 AM
    Let the parent group (Preparation) decides whether to continue execution TSManager 4300 (0x10CC) 2/17/2016 11:38:35 AM
    The execution of the group (Preparation) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 4300 (0x10CC) 2/17/2016 11:38:35 AM
    Failed to run the last action: Check Readiness. Execution of task sequence failed.
    Unspecified error (Error: 80004005; Source: Windows) TSManager 4300 (0x10CC) 2/17/2016 11:38:35 AM
    Set authenticator in transport TSManager 4300 (0x10CC) 2/17/2016 11:38:35 AM
    Task Sequence Engine failed! Code: enExecutionFail TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    **************************************************************************** TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Task sequence execution failed with error code 80004005 TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Cleaning Up. TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Removing Authenticator TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Cleaning up task sequence folder TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Failed to delete directory ‘C:\_SMSTaskSequence’ TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    SetNamedSecurityInfo() failed. TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    SetObjectOwner() failed. 0x80070005. TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca … TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Successfully unregistered Task Sequencing Environment COM Interface. TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Executing command line: “C:\Windows\CCM\TsProgressUI.exe” /Unregister TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    ==========[ TsProgressUI started in process 3928 ]========== TsProgressUI 4592 (0x11F0) 2/17/2016 11:38:58 AM
    Command line: “C:\Windows\CCM\TsProgressUI.exe” /Unregister TsProgressUI 4592 (0x11F0) 2/17/2016 11:38:58 AM
    Unregistering COM classes TsProgressUI 4592 (0x11F0) 2/17/2016 11:38:58 AM
    Unregistering class objects TsProgressUI 4592 (0x11F0) 2/17/2016 11:38:58 AM
    Shutdown complete. TsProgressUI 4592 (0x11F0) 2/17/2016 11:38:58 AM
    Process completed with exit code 0 TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Successfully unregistered TS Progress UI. TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Start to cleanup TS policy TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    End TS policy cleanup TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    GetTsRegValue() is unsuccessful. 0x80070002. TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    End program: TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Error executing Task Sequence Manager service. Code 0x80004005 TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Sending error status message TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Set authenticator in transport TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
    Successfully finalized logs to SMS client log directory from C:\Windows\CCM\Logs TSManager 4300 (0x10CC) 2/17/2016 11:38:58 AM
     2185188320 (0x823F53E0) 1/1/1601 12:00:00 AM
    Registering COM classes TsProgressUI 5104 (0x13F0) 2/17/2016 1:29:57 PM
    sbModulePath = C:\Windows\CCM\TsProgressUI.exe TsProgressUI 5104 (0x13F0) 2/17/2016 1:29:57 PM
    Shutdown complete. TsProgressUI 5104 (0x13F0) 2/17/2016 1:29:57 PM
    Successfully intialized Logging for TS Manager. TSManager 1404 (0x057C) 2/17/2016 1:30:14 PM
    Commandline: C:\Windows\CCM\TSManager.exe /service TSManager 1404 (0x057C) 2/17/2016 1:30:14 PM
    Successfully registered Task Sequencing COM Interface. TSManager 1404 (0x057C) 2/17/2016 1:30:14 PM
    Executing as a service TSManager 1404 (0x057C) 2/17/2016 1:30:14 PM
    Started ServiceMain TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Task Sequence Manager executing as service main thread TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Reading logging settings from TS environment to set TS logging TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca … TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Waiting for CcmExec service to be fully operational TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    CcmExec service is up and fully operational TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Remediating TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Error getting system isolation info. Code 8027000C TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Remediation failed. Code 8027000C TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Remediation failed with error code 8027000C TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Parsing task sequence . . . TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Task sequence schema version is 3.00 TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Current supported schema version is 3.10 and 3.00 TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Starting Task Sequence Engine . . . TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    **************************************************************************** TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Set a global environment variable _SMSTSNextInstructionPointer=0 TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Set a global environment variable _SMSTSInstructionTableSize=16 TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Set a global environment variable SMSTSRebootRequested= TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Set a global environment variable SMSTSRebootDelay= TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Set a global environment variable SMSTSRebootMessage= TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Set a global environment variable SMSTSRebootReason= TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Set a global environment variable SMSTSRetryRequested= TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    The task execution engine started execution TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Set authenticator in transport TSManager 580 (0x0244) 2/17/2016 1:30:14 PM
    Start executing an instruction. Instruction name: Preparation. Instruction pointer: 0 TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a global environment variable _SMSTSCurrentActionName=Preparation TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a global environment variable _SMSTSNextInstructionPointer=0 TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    The group (Preparation) has been successfully started TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set authenticator in transport TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Updated security on object C:\_SMSTaskSequence. TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a global environment variable _SMSTSNextInstructionPointer=1 TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a TS execution environment variable _SMSTSNextInstructionPointer=1 TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a global environment variable _SMSTSInstructionStackString=0 TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a TS execution environment variable _SMSTSInstructionStackString=0 TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Save the current environment block TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a global environment variable _SMSTSLastActionRetryCount=0 TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Start executing an instruction. Instruction name: Check Readiness. Instruction pointer: 1 TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a global environment variable _SMSTSCurrentActionName=Check Readiness TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a global environment variable _SMSTSNextInstructionPointer=1 TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a local default variable OSDCheckFreeDiskSpace TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a local default variable OSDCheckMemory TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a local default variable OSDCheckOSType TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a local default variable OSDCheckProcessorSpeed TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a local default variable OSDFreeDiskSpace TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a local default variable OSDMemory TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a local default variable OSDOSType TSManager 580 (0x0244) 2/17/2016 1:30:15 PM
    Set a local default variable OSDProcessorSpe

  20. Hi, As I could see it fails at check readiness so make sure you have minimum requirement for installing windows 10 and also if you have any third party then uninstall it and try .
    If it fails again then send me all logs which get created under smsts folder

    1. thank you !!…. what minimum requirements ? and or software ? right now it’s Windows 7 64bit and the only Anti Virus is SCEP

  21. Hi it’s ur machine memory here is what I found in the log
    Memory requirement validation failed. (Required: 2048 MB, Found: 1936 MB) CheckReadiness 5344 (0x14E0) 2/17/2016 11:38:34 AM
    So either edit the minimum requirements in the ts or increase ur RAM

  22. Hi

    upgrade works fine, but need to know how to hide login scree until all software’s are installed.
    once Win10 o\OS get upgraded, it shows login screen, users will be able to login to machine and work, same time application upgrade will be happening, as users login some application upgrade is not happening, need to know how can i suppress login scree untill all apps are upgraded.

  23. Hi

    upgrade works fine, but need to know how to hide login scree until all software’s are installed.
    once Win10 o\OS get upgraded, it shows login screen, users will be able to login to machine and work, same time application upgrade will be happening, as users login some application upgrade is not happening, need to know how can i suppress login scree untill all apps are upgraded.

    1. you can hide the explorer shell as the installation has not yet completed, using the HIDESHELL = YES command in customsettings.ini

  24. Hi

    Getting login windows before task sequnce get over, all app upgrade happen after login, need to suppress user login until task sequence is fully done.

  25. My machines are doing the upgrade but a lot of them seem to not finish the TS. When i look back in software center it says installing instead of finished. Any ideas why. I do not think it’s running my tasks after the upgrade either.

  26. hi guys, followed all the steps. Windows vnext upgrade appears in available software on client, when i select install i get “unable to make changes to your software” any ideas?

  27. hi stu check if your sccm client is healthy..could you check tsagent.log on server side and send it for more understanding

  28. On some PC it is working ok, on same id failed.

    log:

    Working dir ‘C:\_SMSTaskSequence\Packages\K01000A1’ InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    Executing command line: Run command line InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    CreateProcess( NULL, (LPWSTR)m_sCommandLine.c_str(), NULL, NULL, TRUE, bNT ? CREATE_UNICODE_ENVIRONMENT : 0, m_pEnvironmentBlock, pszWorkingDir, &si, &pi ), HRESULT=800700d8 (e:\qfe\nts\sms\framework\core\ccmcore\commandline.cpp,1019) InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    CreateProcess failed. Code(0x800700D8) InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    Command line execution failed (800700D8) InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    clCommandLine.Execute( uOptions, pszWorkingDir, lpDesktop ), HRESULT=800700d8 (e:\qfe\nts\sms\client\osdeployment\installsoftware\runcommandline.cpp,562) InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    Failed to execute command line ‘”C:\_SMSTaskSequence\Packages\K01000A1\Setup.exe” /Auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /PostOobe C:\_vNextUpgrade /PostRollback C:\_vNextUpgrade’ .
    Unknown error (Error: 800700D8; Source: Unknown) InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    ReleaseSource() for C:\_SMSTaskSequence\Packages\K01000A1. InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    reference count 1 for the source C:\_SMSTaskSequence\Packages\K01000A1 before releasing InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    Released the resolved source C:\_SMSTaskSequence\Packages\K01000A1 InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=800700d8 (e:\qfe\nts\sms\client\osdeployment\installsoftware\main.cpp,372) InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    Install Software failed to run command line, hr=0x800700d8 InstallSoftware 25.2.2016 12:57:01 3164 (0x0C5C)
    Process completed with exit code 2147942616 TSManager 25.2.2016 12:57:02 3864 (0x0F18)
    !——————————————————————————————–! TSManager 25.2.2016 12:57:02 3864 (0x0F18)
    Failed to run the action: Upgrade Windows.
    Unknown error (Error: 800700D8; Source: Unknown) TSManager 25.2.2016 12:57:02 3864 (0x0F18)

  29. Hey Sandi,

    As per your logs I found that package is being downloaded but unable to execute the command line so cause for this is some uncompitable software.
    So do one thing copy the media locally on the machine where it is failing and run the setup and check whether it gives you any UN compitable software’s.
    Make sure you don’t have any third party antivirus installed if you have then uninstall it.
    Let me know if it works

  30. Task sequence works fine if deployment is set to available. If deployment is set to required, will fail with error 0x00000A58. Anyone with similar behaviour?
    Cheers

  31. Thanks for the guide.

    by the way, can we use our own customised win 10 wim instead of the one in Windows vNext Upgrade.zip?
    if there is missing driver or driver not installed(example: graphic driver), is there any way to add the task to install the drivers of the model of the computer in the upgrade to windows 10 task sequence?
    thanks.

  32. Is there a way to stop the language being set to ENG-US causing issue when users try to log back in after upgraded and keyboard layout has changed.
    Thanks

  33. Nice tutorial

    This is an upgrade Task sequence. Could you please make a task sequence which copy the existing setting (eg language, keyboard layout ) and implement into upgrade.

    Could you please also make a task sequence for fresh installation where it ask for user in put like
    Security Credential , Computer number, organisation unit, language, timezone

  34. Can you do an in place upgrade for unknown computers (say for example SCCM is new and machiones on the estate don’t have the client installed)?

    1. This upgrade is only for “known” computers – systems that already have an SCCM client. If you want to deploy on systems that already have an OS, you will need to deploy an SCCM client and then proceed with OS deployment, or you can do a bare metal deployment and completely re-image the system.

  35. Hi

    If you have a custom Install.wim. Can you replace the wim from the media with this so that when a client is rebuilt using this TS it gets any customisations that may be wanted and included in the customized wim?

  36. One more thing. Is there a way to get this to display in software centre under operating systems rather than Applications?

  37. This worked like a champ for us in an enterprise environment. But alas the win 10 isnt activated.
    I added the MAK win 10 product key in the product key section in the Upgrade Operation System task sequence section.
    Am I missing something? Should there be some other thing maybe under Options tab?

    Thanks in advance

      1. Yes on that machine i activated with same MAK, no issues.
        I see this from a previous post in this thread:

        Matt,

        You can do this by editing the command line in the “Upgrade Windows” step in the task sequence. If you add the switch that specifies a Windows 10 key, it will automatically activate, as well. The switch to do that is: /pkey XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

        Where would I use this switch if thats what Im missing?

  38. I used this step following the video and it work flawlessly a few months ago, but now i noticed with more testing that it gets hung up on 100% for software updates. Any clue how I could comment that out in the scripts? Seems like if you do a hard reboot, Windows 10 finally cooperates and finishes.

  39. Actually I think the difference is when i first used this and it worked fine until now is i am using contents from a Win 10 1607 version ISO, dont think the power shell scripts like that version in SCCM. So when I removed the media and extracted just Win 10 64 bit ISO (no updated versions) i am seeing the interface difference in upgrade from screeen shots above.

  40. Great, one machine is stuck at 100 % while configuring settings. Hp Zbook 15 g3

    Anyway around this or tweaks in the ps1 scripts? Also how do you get office to activate with the task sequence?

    1. Hi Joe, Not sure about the PS1 scripts…However, to activate office: 2 steps, (Run Command Line)

      I have a KMS server, so I set the Server with the first line (I have machines, not on the domain, so I do set the KMS server) If you have MAK licenses, you can also use the ospp.vbs to set that as well, plenty of docs on it..

      2nd line does the actual activating…The commands need to change, for your version of Windows (the below is for Office 13, x86 on Win 7, x64)

      cscript “%programfiles(x86)%\Microsoft Office\Office15\ospp.vbs” /sethst:My.KMS.Server
      cscript “%programfiles(x86)%\Microsoft Office\Office15\ospp.vbs” /act

  41. Hi larry,

    What I did was made another task sequence in SCCM so basically I did what Josh did above using media from Windows 10 (no updated versions) iso then I disabled the Install Software Updates to prevent any hung ups at 100 % then when Windows 10 is upgraded on a Win 7 machine, users will need to open Word which then will reconfigure itself on the upgraded OS. I made another package in SCCM, just a new tasksequence with a script that inserts the Mak Key so i made that as available and in my instructions to users they click Install and the script will activated office 2013.

    andy, if you have SCCM 2016 or 1602 version of SCCM, you can add conents of your extracted ISO to the operating system

    http://www.windowsnetworking.com/articles-tutorials/windows-10/performing-windows-10-place-upgrades-configmgr-tp3.html

    I use this basically

    cd “C:\Program Files (x86)\Microsoft Office\Office15”

    cscript ospp.vbs /inpkey:XXXXXXXX

    cscript ospp.vbs /act

    I bundled that all up in a ps1 file and in my task sequence i use a run command line: cmd /c powershell.exe -ExecutionPolicy Bypass -File \\IP address\Source\Scripts\ and my ps1 file this works flawlessly.

  42. Hello,
    Solucion for error 0x80004005
    Add user in local group Administrators and if you deploy / upgrade in virtual machine Hyper-V use 3000mb memory.

    Thanks

  43. I’ve got the error code 0x0000A58 when deploying W10Pro (Build 14393), Iv’e finally discover that Mcafee VSE 8 was blocking the process with a Protection access Policy, disabled PAP and works like a charm :)

    Thanks for the post!

    Regards

  44. Hi guys ,
    If there is missing driver or driver not installed(example: graphic driver or network drivers), is there any way to add the task to install the drivers of the model of the computer in the upgrade to windows 10 task sequence?
    we are having issues on performing In-place on SCCM 2012 because of drivers . kindly help
    Thanks in advance

  45. Olá pessoal,

    A página referida para baixar a task sequence, está fora, como posso achar novamente?

  46. Hello
    When running the task sequence I am getting the error 0x00000A58.
    What I have found so far is that Win 10 does not like the installed video driver. Is there a way to make the Task Sequence install (or command line) “Confirm” that it is an issue like you can when it gets to the same step when you run the setup.exe install and bypass this step?

    1. Hi Scott,

      Have you removed the video driver from the driver package used by your task sequence? Seems like that would confirm the issue if that’s the only change you made. You can always check the option to “continue on error” on each task sequence step and review the SMSTS log file to see what went wrong.

      1. Josh

        it is the currently installed Windows 7 driver that seems to stop the upgrade. I have added the check box to Continue on Error.
        When the Win 10 upgrade checks compatibility, it finds the Win 7 Video driver and fails to continue. Unfortunately the Task sequence does not stop and allow me to confirm.

    2. Fixed!
      We changed the Upgrade Windows Command Line to the following and have bypassed the incompatible video driver and re-injected the driver pack later on in the sequence.

      Setup.exe /Auto Upgrade /Compat IgnoreWarning /ShowOOBE none /Quiet /NoReboot /DynamicUpdate Disable /PostOobe %SystemDrive%\_vNextUpgrade\SetupComplete.cmd /PostRollback %SystemDrive%\_vNextUpgrade

  47. Hi ,

    I am using above link provided by you to do In-place upgrade through SCCM 2012 R2 SP1 . I am trying to upgrade window 7 into window 10 through SCCM via task sequence and the upgrade failed with error code Error: 0x4005(16389). Please suggest

    Thanks

  48. = nRequiredMemory, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prestartcheck\osdprestartcheck.cpp,60)]LOG]!>

    

    = nRequiredMemory, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prestartcheck\osdprestartcheck.cpp,60)]LOG]!>

    

    = nRequiredMemory, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prestartcheck\osdprestartcheck.cpp,60)]LOG]!>

  49. Hi Josh, i am having this error “Task Sequence: Windows Upgrade TS 2 has failed with the error code (0x80004005). For more information, contact your system administrator or helpdesk operator.”. i am running Task sequence from sccm 2016 to upgrade windows 7 to windows 10, the TS started from clients though not all but stopped with that error. what do you think is causing this issue

    1. Victor,

      That is a generic task sequence failure error. Post or send the SMSTS.log and you should find some more info there. Thanks,

      Josh

  50. Hello Josh. I was looking your article. I found it very easy to follow. I have downloaded the Windows10Upgrade1506.zip from https://docs.microsoft.com/en-us/windows/deployment/upgrade/upgrade-to-windows-10-with-system-center-configuraton-manager.

    But when i import/create the task sequence i have error:

    System.Runtime.InteropServices.COMException
    The XML content is invalid; check that the XML matches the schema for the SMS task sequence.

    Stack Trace:
    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
    at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
    at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.WmiConnection.TryExecuteMethod(IObjectContext context, Object method, Object target, IObjectSession cache)
    at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.ObjectLibraryImpl.ExecuteMethod(IObjectContext context, IObjectSession cache, Object method, Object target)
    at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.ObjectMethod`1.Execute(IObjectContext context, IObjectSession cache)
    at Microsoft.ConfigurationManagement.Migration.ConfigMgr2012.SMS_TaskSequence.LoadFromXml(IObjectContext context, String Xml)
    at Microsoft.ConfigurationManagement.Migration.ConfigMgr2012.SoftwareDistribution.TaskSequenceLibrary.ResolveDependency(ObjectHandle source, ObjectHandle target, ObjectContext targetContext, ImportSetting setting)
    at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.ObjectLibrary`1.d__6.MoveNext()
    at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.ObjectContext.SaveChanges(IEnumerable`1 values)
    at Microsoft.ConfigurationManagement.Migration.ObjectSerialization.ImportRequest.Submit()
    at Microsoft.ConfigurationManagement.AdminConsole.MigrationAssistant.FileContentPageControl.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
    at Microsoft.ConfigurationManagement.AdminConsole.SmsWizardPage.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
    at Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.PostApply(SmsWizardPage page, BackgroundWorker worker, DoWorkEventArgs e)
    at Microsoft.ConfigurationManagement.AdminConsole.SmsWizardForm.PostApply(BackgroundWorker worker, DoWorkEventArgs e)
    at Microsoft.ConfigurationManagement.AdminConsole.ProgressPage.backgroundWorkerPostApply_DoWork(Object sender, DoWorkEventArgs e)
    at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
    at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

    ——————————-

    Any help please ?

    Best Regards

    1. Hi Nando,

      As stated at the top of the article, the ZIP file with the OS upgrade task sequence is no longer required. The upgrade task sequence is available directly in SCCM now – just right-click task sequences and select it there.

      Thanks,

      Josh

  51. Hi Josh ,
    I can not find the ZIP file for windows 10 at the bottom of the page ?
    can you please attache it here ?

    Thank you

    1. Hello,

      The zip is no longer included because Microsoft now has a “native” task sequence that will deploy the in-place upgrade. This is built into Configuration Manager now when you create a new task sequence.

  52. i have a problem..

    my log;

    /code 2019-05-14 17:43:50, Error MOUPG CSystemHelper::CheckConnectedStandby(642): Result = 0x80070057
    2019-05-14 17:44:16, Error MOUPG CDlpActionProductKeyValidate::ReportDownlevelInstallChannel(3102): Result = 0x80070490
    2019-05-14 17:44:16, Error MOUPG ProductKey: Failed to report Host OS channel to telemetry.
    2019-05-14 17:44:30, Error CSI 00000001 (F) STATUS_OBJECT_NAME_NOT_FOUND #10# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = 654 (‘\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion’), vn = [l:25 ml:26]’CurrentMajorVersionNumber’, kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
    2019-05-14 17:44:30, Error CSI 00000002 (F) STATUS_OBJECT_NAME_NOT_FOUND #9# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:63]’\Registry\Machine\SOFTWARE\Microsoft\Windows NT\CurrentVersion\’, vn = [l:25 ml:26]’CurrentMajorVersionNumber’, ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
    2019-05-14 17:44:30, Error CSI 00000003 (F) STATUS_OBJECT_NAME_NOT_FOUND #38# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = 654 (‘\REGISTRY\MACHINE\SYSTEM\Setup’), vn = [l:7 ml:8]’Compact’, kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
    2019-05-14 17:44:30, Error CSI 00000004 (F) STATUS_OBJECT_NAME_NOT_FOUND #37# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:31]’\Registry\Machine\SYSTEM\Setup\’, vn = [l:7 ml:8]’Compact’, ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
    2019-05-14 17:44:30, Error CSI 00000005 (F) STATUS_OBJECT_NAME_NOT_FOUND #45# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = 604 (‘\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion’), vn = [l:11 ml:12]’BuildBranch’, kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
    2019-05-14 17:44:30, Error CSI 00000006 (F) STATUS_OBJECT_NAME_NOT_FOUND #44# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:63]’\Registry\Machine\SOFTWARE\Microsoft\Windows NT\CurrentVersion\’, vn = [l:11 ml:12]’BuildBranch’, ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
    2019-05-14 17:46:03, Error CSI 00000007 (F) STATUS_OBJECT_NAME_NOT_FOUND #75# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysQueryValueKey(flags = 0, key = 5fc (‘\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts’), vn = [l:21 ml:22]’Arial Nova (TrueType)’, kvic = 2, kvi = 2, disp = 0)[gle=0xd0000034]
    2019-05-14 17:46:03, Error CSI 00000008 (F) STATUS_OBJECT_NAME_NOT_FOUND #74# from Windows::Rtl::SystemImplementation::CKey::QueryValue(flags = 0, kn = [l:69]’\Registry\Machine\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts\’, vn = [l:21 ml:22]’Arial Nova (TrueType)’, ic = KeyValuePartialInformation, info = {l:0 b:}, disp = 0)[gle=0xd0000034]
    2019-05-14 17:46:26, Error CONX Windows::Compat::Appraiser::AssetUtils::GetProgramNameAndRegistryPathFromFile (695): App should have registry path, swallowing error.[gle=0x8007139f]
    2019-05-14 17:46:38, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl > > >::Suspend(1066): Result = 0xC1800104
    2019-05-14 17:46:39, Error MOUPG CSetupManager::ExecuteInstallMode(807): Result = 0xC1900208
    2019-05-14 17:46:39, Error MOUPG CSetupManager::ExecuteDownlevelMode(390): Result = 0xC1900208
    2019-05-14 17:46:44, Error MOUPG CDlpTask::Cancel(980): Result = 0xC1800104[gle=0x00000003]
    2019-05-14 17:46:44, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl > > >::CheckInitialized(228): Result = 0x8000000A[gle=0x00000003]
    2019-05-14 17:46:44, Error MOUPG CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl > > >::Cancel(154): Result = 0x8000000A[gle=0x00000003]
    2019-05-14 17:46:44, Error MOUPG CDlpTask::Cancel(1031): Result = 0x8000000A[gle=0x00000003]
    2019-05-14 17:46:44, Error MOUPG CDlpManager::Reset(1612): Result = 0x8000000A[gle=0x00000003]
    2019-05-14 17:46:44, Error MOUPG SetupManager: Reset WinDlp State failed with error [0x8000000A][gle=0x00000003]
    2019-05-14 17:46:44, Error MOUPG SetupManager: Failed requested cleanup: [0x8000000A][gle=0x00000003]
    2019-05-14 17:46:44, Error MOUPG CSetupManager::Execute(282): Result = 0xC1900208[gle=0x00000003]
    2019-05-14 17:46:44, Error MOUPG CSetupHost::Execute(400): Result = 0xC1900208[gle=0x00000003]

  53. Shashikant yadav

    Hi,

    I have tried to reimaged system with PXE boot with TS 1903, but getting error 0*00000057 after disk formatting. can you please help me to get issue fixed.

    Regards
    Shashikant

Leave a Comment

Your email address will not be published.