none
Updating to Windows 10 1709 failed - Error code 0x80004005

    Question

  • Hello;

    I'm using MDT 2013, build 8450, with Windows 10 1709 ADK installed.

    From an Windows 10 client in build 1607, I'm trying to execute an upgrade task sequence to upgrade my windows 10 client version to 1709, all drivers injected is good, during the task sequence, it starting to Upgrade the OS, but not finish this step.

    Here is my BDD.log

    <![LOG[Property TaskSequenceID is now = 012]LOG]!><time="14:34:18.000+000" date="01-24-2018" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[Property TaskSequenceName is now = Udpate-Win10-1709]LOG]!><time="14:34:18.000+000" date="01-24-2018" component="Wizard" context="" type="1" thread="" file="Wizard">
    <![LOG[File C:\MININT\Scripts\LTIBootstrap.vbs already exists in Target]LOG]!><time="14:35:42.000+000" date="01-24-2018" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[LTICopyScripts processing completed successfully.]LOG]!><time="14:35:42.000+000" date="01-24-2018" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts">
    <![LOG[Property SourcePath is now = \\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2]LOG]!><time="14:35:42.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[LTI upgrade OS using  \\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2]LOG]!><time="14:35:42.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[New ZTIDiskPartition : \\LAPS-PC1\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\LAPS-PC1\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Upgrading from \\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2\setup.exe using command: "\\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /InstallDrivers C:\MININT\Drivers /DynamicUpdate Disable /ImageIndex 5 /compat IgnoreWarning]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[About to run command: "\\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /InstallDrivers C:\MININT\Drivers /DynamicUpdate Disable /ImageIndex 5 /compat IgnoreWarning]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command has been started (process ID 5860)]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 5860)]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Return code from command = -1047526908]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Setup failed to upgrade OS from  \\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2\setup.exe, rc = -1047526908]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[ZTI ERROR - Non-zero return code by LTIApply, rc = 1]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[Command completed, return code = -2147467259]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property RetVal is now = -2147467259]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[CleanStartItems Complete]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Unregistering TSCore.dll.]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: wscript.exe "\\svcdc-test\deploymentshare$\Scripts\LTICleanup.wsf"]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.3.8450.1000]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Removing AutoAdminLogon registry entries]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Re-enabling UAC for built-in Administrator account]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Removing Windows 10 Upgrade registry entry]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[VSSMaxSize not specified using 5% of volume.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Logs contained 43 errors and 10 warnings.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[No Windows PE image to delete.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Checking mapped network drive.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[testing drive Z: mapped to \\svcdc-test\deploymentshare$]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[testing drive Y: mapped to \\192.168.0.3\DeploymentShare$]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Disconnecting drive Y: mapped to \\192.168.0.3\DeploymentShare$]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up C:\MININT directory.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    
    Any idea please?

    Wednesday, January 24, 2018 1:46 PM

All replies

  • Please provide additional details - when does the upgrade process fail? If it fails during one of the downlevel phases, you will not find any clues in the MDT logs - MDT initiates the upgrade process by running setup.exe with various parameters, however, then Windows Setup handles the update process. This article goes into great detail how to troubleshoot upgrade errors: https://docs.microsoft.com/en-us/windows/deployment/upgrade/resolve-windows-10-upgrade-errors

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Thursday, January 25, 2018 7:12 AM
  • The task sequence starts well, inject drivers, and launch the "update process".

    After about 30s/1 min, it failed with the logs I provided.

    I'm using an windows 10 Iso file from MS Website (MSDN access); So I suppose this is the good one. I'm not using an personalized wim...

    Thursday, January 25, 2018 9:14 AM
  • In this case, you will need to grab Panther logs as outlined in the article I linked above. MDT logs will not provide any clues what went wrong during the update process. The location of these logs moves around depending on the setup phase, so pinpointing them down could be a bit of a challenge.

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Thursday, January 25, 2018 9:37 AM
  • Error code is : -1047526908 after setup.exe command launched.
    If I convert it into hex code : C190 0204

    If i'm not wrong, I'm in phase 2 the "SAFE OS PHASE"..

    Thursday, January 25, 2018 9:37 AM
  • And 0204 seems to be : 

    0xC0000204

    STATUS_RESOURCE_LANG_NOT_FOUND

    Indicates the specified resource language ID cannot be found in the image file.

    Thursday, January 25, 2018 9:42 AM
  • Maybe because the OS installed have additional languages pack installed..

    Thursday, January 25, 2018 9:43 AM
  • Could you grab your setupact and setuperr log files and post them here? 

    Also, make sure your target OS matches the language of your ISO file. Depending on how you install OS and inject lang packs, you may run into a hard block due to language incompatibilities: http://vacuumbreather.com/index.php/blog/item/31-mastering-windows-10-language-packs


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Thursday, January 25, 2018 10:01 AM
  • 80040005 has multiple causes.

    Litetouch deployment failed, Return Code = -2147467259  0x80004005

    For more information, consult the task sequencer log ...\SMSTS.LOG.

    Logs contained 43 errors and 10 warnings.

    Search for these panther logs and post any that you find using one drive or drop box share links:

    setuperr.log
    setupact.log
    Setupmem.dmp
    setupapi.dev.log
    BlueBox.log

    C:\$Windows.~BT\Sources\Rollback
    $Windows.~bt\Sources\Rollback\setupmem.dmp
    $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

    Windows\Logs\Mosetup




    Thursday, January 25, 2018 10:06 AM
  • Here is the setuperr.log:

    2018-01-25 10:10:03, Error                 MOUPG  MigChoice: Selected install choice is not available.
    2018-01-25 10:10:03, Error                 MOUPG  CDlpActionCompat::ExecuteMigChoiceScan(1629): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 MOUPG  CDlpActionCompat::ExecuteRoutine(623): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class ICompatAction> > > >::Execute(441): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 MOUPG  CDlpTask::ExecuteAction(3243): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 MOUPG  CDlpTask::ExecuteActions(3397): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 MOUPG  CDlpTask::Execute(1631): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 MOUPG  CSetupManager::ExecuteTask(1953): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 MOUPG  CSetupManager::ExecuteTask(1916): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 MOUPG  CSetupManager::ExecuteInstallMode(648): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(376): Result = 0xC1900204
    2018-01-25 10:10:03, Error                 SP     CSetupPlatform::ResurrectNewSystem: Failure: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: Le fichier sp�cifi� est introuvable. [0x00000002] __cdecl UnBCL::FileStream::FileStream(const class UnBCL::String *,enum UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)[gle=0x00000002]
    2018-01-25 10:10:20, Error                 MOUPG  CDlpTask::Cancel(979): Result = 0xC1800104
    2018-01-25 10:10:20, Error                 MOUPG  CDlpTask::Cancel(983): Result = 0xC180010A
    2018-01-25 10:10:20, Error                 MOUPG  CDlpTask::Cancel(979): Result = 0xC1800104
    2018-01-25 10:10:44, Error                 MOUPG  CSetupManager::Execute(222): Result = 0xC1900204
    2018-01-25 10:10:45, Error                 MOUPG  CSetupHost::Execute(370): Result = 0xC1900204
    2018-01-25 10:10:45, Error                 MOUPG  CDlpManager::AsyncSerializeDisable(471): Result = 0x80070216
    

    Thursday, January 25, 2018 10:11 AM
  • Other logs are needed: see earlier post

    Result = 0xC1900204

    Result = 0xC1800104

    Result = 0x80070216

    Thursday, January 25, 2018 10:23 AM
  • I only got setuperr.log & setupact.log.

    Others from rollback folder are missing.

    I'm checking smsts.log.

    For what I know, my 1607 language Image setup is is :

    UI in French
    Fallback en-us

    And I have additionnal languages fr-fr, us-us, and it-it.

    Maybe the pb is that the source image is en-us (fallback language) and I'm trying to update my installation with an french iso..


    • Edited by Frédéric.G Thursday, January 25, 2018 12:58 PM
    Thursday, January 25, 2018 12:53 PM
  • setupact.log is here : https://pastebin.com/YfSPtEUh
    Thursday, January 25, 2018 1:53 PM
  • This was the final reporting event:  Reporting error event -> [0xC1900204, 0x4000A]

    Problem is second boot phase.

    {4 SP_EXECUTION_OOBE_BOOT

    A SP_EXECUTION_OP_PREPARE_FIRST_BOOT}

    Language did not appear to be a problem by this entry:

    2018-01-25 10:10:03, Info                  CONX   ConX::Compatibility::CSystemAbstraction::TargetLanguageIsCompatibleForUpgrade: Target language fr-FR is compatible with the host language (lang.ini path: C:\$Windows.~BT\Sources\lang.ini).

    Result = 0xC1800104

    {0x00000104

    STATUS_REPARSE

    A reparse should be performed by the Object Manager because the name of the file resulted in a symbolic link.}

    2018-01-25 10:10:03, Error                 MOUPG  MigChoice: Selected install choice is not available.
    2018-01-25 10:10:03, Error                 MOUPG  CDlpActionCompat::ExecuteMigChoiceScan(1629): Result = 0xC1900204

    {0xC0000204

    STATUS_RESOURCE_LANG_NOT_FOUND

    Indicates the specified resource language ID cannot be found in the image file.} 

    It is unclear how to address the image file.

    At this point consider running through every item in this check list and attempting an upgrade:

    Run through this check list before the next upgrade attempt:

    1) remove nonessential hardware
    docks
    USB devices
    printers
    headset
    speakers
    bluetoot devices
    USB drives (other than a windows 10 iso if used for the upgrade)
    USB Wireless Mouse or Keyboard Receiver, USB Wireless Network Card,



    2) These should be the only attached devices:
    wired mouse
    wired keyboard
    monitor

    Any of these that have been done in the past week are not necessary to repeat:


    3) open administrative command prompt and type or copy and paste: (repair file system)
    chkdsk /x /f /r 
    This may take many hours so plan to run overnight
    Find the chkdsk report in the event viewer using the information in this link and post into the thread:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials 

    4) open administrative command prompt and copy and paste: (repair operating system)
    sfc /scannow 
    dism /online /cleanup-image /restorehealth 
    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    5) update windows (have all recommended updates installed) and reboot after updates

    6) uninstall all non-Microsoft antivirus software
    (This includes always on and manual software.)

    7) Verify that the drive has > 27 GB free space (At least 25 GB is needed for creating dumps)

    8) Place the computer in clean boot:
    https://support.microsoft.com/en-us/...oot-in-windows
    How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

    9) Remove all unused SATA devices

    10) Uninstall non-Microsoft disk encryption software

    11) Run disk cleanup to clean temporary and system files

    12) 1. Browse to "C:\Windows\SoftwareDistribution\Download" and delete the contents of the folder.
    2. Press Windows key + X > Click Command Prompt (Admin) then type "wuauclt.exe /updatenow".
    Hit Enter
    3. Open Control Panel > Windows Update and Windows 10 should begin downloading
    https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc

    13) Another command you should run is the cleanup driver. Press Windows key + X, click Command Prompt (Admin) then type the following command and hit Enter on your keyboard. Restart your computer when complete. This should help with the notorious failed or non-responsive installation during the driver migration.

    rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN

    14) 1. Check Manufacturer’s Website to Find Out if Your System is Compatible
    Manufacturers of various brands actually do a good job of maintaining a list of systems that are compatible with specific versions of Windows 10. Check the following links to see if your system is supported by the Creators Update. If an OEM indicates a particular model is not compatible with Windows 10 1709, it is possible you could still install the update using the clean install method. Of course, the best way to do this is to ensure you have a good backup plan. Windows 10 has included a rollback feature since the first release, but it’s not perfect, so I wouldn’t count on it too much.

    Hewlett Packard (HP) /Compaq:  https://support.hp.com/us-en/document/c05195282
    Dell Inc:  http://www.dell.com/support/article/us/en/19/sln297954/dell-computers-tested-for-windows-10-fall-creators-update-and-previous-versions-of-windows-10?lang=en
    Lenovo:  https://support.lenovo.com/us/en/solutions/ht501286
    Acer
    Samsung:  https://www.samsung.com/us/support/windows10/
    Sony Vaio:  https://esupport.sony.com/US/p/os10upgrade.pl?
    Toshiba:  http://win10upgrade.toshiba.com/win10anniv/modellist.aspx?region=TAIS&lang=en&country=US
    Packard Bell:  http://www.packardbell.com/index.html
    MSI:  https://us.msi.com/support
    ASUS:  https://www.asus.com/event/2016/osupdate/

    15) Check for a BIOS upgrade

    Friday, January 26, 2018 12:50 AM

  • Hello Guys,

    1709 installer was flagging Nero Burning ROM as blocking the update and telling me to remove it manually. And as many others, I've never had Nero installed on this computer, so there was nothing to uninstall. Well, here's the kicker...

    The Win10 1709 update installer checks for programs with compatibility issues ON YOUR ENTIRE DISK! It does not limit the check to programs that are actually installed on your machine.

    Step 1: Go with below URL and Download  http://m.majorgeeks.com/mg/getmirror/uninstall_this_app_now_powershell_script,1.html

    appraiser.zip file , 

    Step 2 : Run the Bat file in Powershell . in program file it will show the blocking file . delete or remove from the file , 

    step 3: try to install the file again , it will work 100 for error code 

    0x80004005

    Regqrds

    Athul wiki


    Friday, June 22, 2018 6:55 PM
  • Hi,

    I tried to run the PowerShell script "AppRaiser" from Windows 7 Enterprise x64 before upgrade, but I got errors.

    Does you known if a minimum PowerShell version is required to run this script, no mention in the documentation ?

    If I could use this tool, it will be very interesting.

    ------------

    In my case, I'm sure that I have a full functional and working solution to upgrade from Windows 7 x64 Enterprise to Windows 10 LTSB 2015 Enterprise because I as ale to do it without problem. I'm using MDT 2013 Update 2 Build 8450 with normal client upgrade Task Sequence + disabling "Install applications" to do upgrade only.

    NOTE: It's impossible to upgrade from Windows 7 to Windows 10 LTSB 2016 because Microsoft block this option, but with LTSB 2015 it's possible !)

     I upgraded many computers without problem, but I have somewhat computers that I can't and I got an error "0x80004005".

    The analysis of setupact.log give a lot of information, but nothing really clear on specific step that I could confirm the cause of this issue. But one thing is sure, on almost "clean Windows 7" computers the upgrade process is working fine, I'm suspecting on most dirty and older installation that something block the process (incompatible application, bad registry key, ...).

    In hope, this tool could find the issue. Please let me known if this tool could be run well with Win 7 SP1 x64 with default PowerShell version (aka PowerShell 3.0).

    Thursday, August 30, 2018 8:20 PM
  • NOTE: The script error is talking about "Get-Content" is unable to link "TotalCount" parameter and after "Split-Path" is Null like a variable somewhere is not able to find a value.
    Thursday, August 30, 2018 8:26 PM
  • Hi, 

       i understood your issue , this script is created only to upgrade the windows 10 1703 version to 1709 version.

    The Script won't work in windows 7.

    Updating to Windows 10 1709 failed - Error code 0x80004005

    The solution which i provide is total different from your issue.

    Regards

    Athul M

    Thursday, October 11, 2018 4:10 PM