The windows 10 fall upgrade 1709 fails after about 45% mark.. Then gives an error message and returns system to 1703

Anonymous
2017-11-30T19:59:13+00:00

I have tried all the suggestions on my laptop to complete the upgrade to fall creators 1709.  

I have tried the trouble shoot the upgrade (It always fins registry errors after the update...  I run it a couple of times and the second time the registry errors are gone but come back after trying the 1709 update)

I have tried the upgrade by doing the manual update

I have tried resetting all of update... and then trying the update again

I have tried by unplugging the Ethernet cable

I have done a chkdsk c: /f

I have tried Regcure pro (as recommended by Microsoft on a support page - they are a Microsoft partner)

I have tried going back to earlier backups of the laptop..

All end in the same way...

The updates fail after 45% with a old style popup box .. saying windows can not configure one of the system components...

I have tried many options...  but no solution...

I have spent over 80 hours working on this issue...  I really do not want to do a full reinstall of the laptop.... 

Help!!!

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

94 answers

Sort by: Oldest
  1. Anonymous
    2018-02-06T03:34:32+00:00

    Here is PART of setuperr.log

    ends with

    2018-02-05 21:28:51, Error      [0x030153] CMI    Callback_CMI_ConfigInstall: CBS startup processing failed.

    2018-02-05 21:28:51, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation.]

    2018-02-05 21:30:22, Info       [0x070042] DIAG   CallBack_DiagnosticDataSend: Called with notification for Error published by ErrorHandler

    2018-02-05 21:30:22, Info                  DIAG   CallBack_DiagnosticDataSend: Setup was started from Phase 4. Disabling Diagnostics [DiagnosticDataSend] in this scenario

    2018-02-05 21:30:22, Info       [0x090095] PANTHR WdsExitImmediate called!  Execution will stop, and the queue won't be saved.

    2018-02-05 21:30:22, Info       [0x030023] CMI    Callback_CMI_ConfigInstall: Exit.

    2018-02-05 21:30:22, Info       [0x09008c] PANTHR SeqExecute -- stopping, since WdsExitImmediate() was called

    2018-02-05 21:30:22, Info       [0x090086] PANTHR pWorkerThreadFunc -- Stopping

    2018-02-05 21:30:22, Info       [0x090086] PANTHR pWorkerThreadFunc -- Stopping

    2018-02-05 21:30:22, Info       [0x090086] PANTHR pWorkerThreadFunc -- Stopping

    2018-02-05 21:30:23, Info                  PANTHR DeleteCriticalSection for pExecQueue->csLock;

    2018-02-05 21:30:23, Info       [0x0605a6] IBS    Requested UI to hide the language and locale selection pages.

    2018-02-05 21:30:23, Info       [0x090081] PANTHR Destroying any unreferenced modules! (SEQ6)

    2018-02-05 21:30:23, Info       [0x0601d7] IBS    InstallWindows:Error Type = 3211266

    2018-02-05 21:30:23, Info       [0x090009] PANTHR CBlackboard::Close: c:\windows\panther\setupinfo.

    2018-02-05 21:30:23, Info                  SP     WINDEPLOY error code is 0x80004005. Will not attempt uninstall

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-06T03:35:55+00:00

    Here is the compatdataxxxx file

    <?xml version="1.0" encoding="UTF-8"?>

    <CompatReport MigXmlFile="Ebw6bOJBJky-UATB.999.3.8.0.0_APPRAISER_Migration.xml" xmlns="http://www.microsoft.com/ApplicationExperience/UpgradeAdvisor/01012009">

    <System X64Running="True" X64Capable="True"/>

    <Hardware>

    <HardwareItem HardwareType="Setup_BitlockerNoTargetSupport">

    <CompatibilityInfo BlockingType="None"/>

    </HardwareItem>

    <HardwareItem HardwareType="Setup_TargetIsNonStagedBuild">

    <CompatibilityInfo BlockingType="None"/>

    </HardwareItem>

    <HardwareItem HardwareType="Setup_LanguagePackDetected">

    <CompatibilityInfo BlockingType="None"/>

    </HardwareItem>

    <HardwareItem HardwareType="Setup_LicenseActivation">

    <CompatibilityInfo BlockingType="None"/>

    </HardwareItem>

    <HardwareItem HardwareType="Setup_PendingFirmwareUpdateWithPower">

    <CompatibilityInfo BlockingType="None"/>

    </HardwareItem>

    <HardwareItem HardwareType="Setup_FlightSigningEnabled">

    <CompatibilityInfo BlockingType="None"/>

    </HardwareItem>

    <HardwareItem HardwareType="Setup_SecureBoot">

    <CompatibilityInfo BlockingType="None"/>

    </HardwareItem>

    </Hardware>

    <SystemInfo OSMinorVersion="0" OSMajorVersion="10" UplevelEdition="Windows 10"/>

    <Devices/>

    <DriverPackages>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem10.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem14.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem32.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem5.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem18.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem25.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem26.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem33.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem19.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem30.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem13.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem34.inf"/>

    <DriverPackage HasSignedBinaries="False" BlockMigration="True" Inf="oem43.inf"/>

    <DriverPackage HasSignedBinaries="False" BlockMigration="True" Inf="oem42.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem8.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="True" Inf="oem6.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="False" Inf="oem28.inf"/>

    </DriverPackages>

    <Programs/>

    </CompatReport>

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-06T13:49:37+00:00

    Hi Andrew,

    Thanks. I finally found the solution to my problem here: https://forums.iis.net/t/1229869.aspx. The Wireless broadcom driver, even after uninstalling leave some registry entries that caused the problem. I de-activated the Wireless device in BIOS, removed the driver completely, did not allowed Windows Update to update the driver and finally went thorugh the registry and deleted every reference to Broadcom I could find. "After a bunch of digging, I found my problem was that my Broadcom Wireless driver had added some registry keys to HKLM\SYSTEM\CurrentControlSet\Control\Cryptography\Providers and iissetup.exe was just picking the first provider from the list, which was the Broadcom one, and failing."

    After i did that, I also proceed with the USB-ISO created installation(Setup) without any connection to Internet (unplug Ethernet cable) and I also clicked to not make updates before installing(which is the recommended option during setup).

    Then I am now with 1709 with latest January updates. Wireless Broadcom driver is back enabled up and running as well.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-06T16:59:36+00:00

    Here is my setupERR.log file  (Note.. I hav over 200GB spare disk space)

    2018-02-05 19:51:47, Error                 MOUPG  CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1066): Result = 0xC1800104

    2018-02-05 19:56:42, Error                 SP     CDownloadDUUpdates::DoExecuteInternal: Did not find hard disk space needed, when update cab files will not be extracted. This is unexpected! hr = 0x8000ffff

    Look at the setupact.log at these times for context.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-02-06T17:02:58+00:00

    <DriverPackage HasSignedBinaries="False" BlockMigration="True" Inf="oem43.inf"/>

    <DriverPackage HasSignedBinaries="False" BlockMigration="True" Inf="oem42.inf"/>

    <DriverPackage HasSignedBinaries="True" BlockMigration="True" Inf="oem6.inf"/>

    Any clues in those?

    Was this answer helpful?

    0 comments No comments