1703 - 1709 update fails, "could not configure on computer's hardware"

Page 1 of 3 123 LastLast

  1. Posts : 46
    Windows 10
       #1

    1703 - 1709 update fails, "could not configure on computer's hardware"


    Howdy,

    Trying to update from this version:



    And it fails with this error:



    C: is an SSD with a single partition and >100gb space

    Event viewer isn't showing anything helpful that I can see, under WindowsUpdateClient it shows:

    "Installation Successful: Windows successfully installed the following update: Feature update to Windows 10, version 1709"

    Under Windows update it shows:



    I ran SFC /SCANNOW and it reported "Windows Resource Protection did not find any integrity violations"

    I checked WindowsUpdate.log and it doesn't seem to be showing anything useful, lots of "Uknown GUID entries" whatever that means and the only variation is:

    2017/10/24 20:29:05.6742348 2260 17332 Unknown( 14): GUID=05071160-6867-365e-53f1-a3bef8bfcdc3 (No Format Information found).
    2017/10/24 20:29:05.7723300 2260 17332 Unknown( 26): GUID=05071160-6867-365e-53f1-a3bef8bfcdc3 (No Format Information found).
    2017/10/24 20:29:05.8257790 2260 17332 Unknown( 17): GUID=580dee40-4d23-379f-0b70-358e2caca1af (No Format Information found).
    2017/10/24 20:29:10.4848708 3804 8588 Unknown( 12): GUID=26bba210-72d3-3f28-a89e-6bdc4716006d (No Format Information found).
    2017/10/24 20:29:10.4848894 3804 8588 Unknown( 18): GUID=8bc93df4-dfb7-3bd8-4da6-97dda6e01d4f (No Format Information found).
    2017/10/24 20:32:52.8681073 11448 928 AppAU [0]2CB8.03A0::10/24/2017-20:32:52.868 [dll]* START *
    2017/10/24 20:32:52.8682653 11448 928 AppAU [0]2CB8.03A0::10/24/2017-20:32:52.868 [dll]Flight settings ring provisioned default, range-checked minimum search interval: 20 hours
    2017/10/24 20:32:52.8682658 11448 928 AppAU [0]2CB8.03A0::10/24/2017-20:32:52.868 [dll]Skipping app au: duration since last check is too short (46896 < 72000)
    2017/10/24 20:32:52.8683380 11448 928 AppAU [0]2CB8.03A0::10/24/2017-20:32:52.868 [dll]* END *, exit code = 0x00000000
    2017/10/24 20:33:22.2294856 10668 11736 Unknown( 10): GUID=f1534484-4bc1-33f5-b01b-a6144c89bce0 (No Format Information found).
    2017/10/24 20:33:24.4322310 10668 11736 Unknown( 11): GUID=f1534484-4bc1-33f5-b01b-a6144c89bce0 (No Format Information found).
    2017/10/24 20:42:52.9951420 9508 17384 Unknown( 10): GUID=1bce64d0-3b5c-3a28-bd28-0e6a0b1dc374 (No Format Information found).
    2017/10/24 20:42:53.0027441 3804 1744 Unknown( 49): GUID=5ef3a3ec-77ec-365d-4b50-112be6fe4141 (No Format Information found).
    2017/10/24 20:42:53.0423969 3804 11440 Unknown( 25): GUID=9706eed1-c75b-36dc-efef-73a498adc0c2 (No Format Information found).
    2017/10/24 20:42:53.0432259 3804 11440 Unknown( 11): GUID=37ce7420-0f5c-3a93-292a-f53914190c53 (No Format Information found).
    Tried twice and it's failed both times. Really need some help please! :)
      My Computer


  2. Posts : 258
    Windows 10 Pro
       #2

    Have you got USB devices attached? Best to remove everything apart from essential items just in case
      My Computer


  3. Posts : 46
    Windows 10
    Thread Starter
       #3

    I have a USB wireless battery free mouse, a USB keyboard and a USB extension cable, I'll try unplugging them next time thanks :)
      My Computer


  4. Posts : 258
    Windows 10 Pro
       #4

    the mouse and kb should be fine but try them directly into the pc instead of the usb extension cable just incase
      My Computer


  5. Posts : 46
    Windows 10
    Thread Starter
       #5

    kingtez1984 said:
    the mouse and kb should be fine but try them directly into the pc instead of the usb extension cable just incase
    Yes they are directly into it, just remembered (well noticed) it's a USB soundcard plugged into the extension cable so I'll unplug that for sure.
      My Computer


  6. Posts : 258
    Windows 10 Pro
       #6

    yeah, usb's are a pain lol
      My Computer


  7. Posts : 46
    Windows 10
    Thread Starter
       #7

    I removed all USB' except my mouse and tried the update via Windows10Upgrade9252.exe and it failed again in the exact same way
      My Computer


  8. Posts : 258
    Windows 10 Pro
       #8

    Anti Virus program possibly lol
      My Computer


  9. Posts : 46
    Windows 10
    Thread Starter
       #9

    The error is post boot screen, pre desktop so it can't be the antivirus.

    Thought possibly it was a permissions problem as unlikely as that'd be so tried running the updater from the built in admin account rather than my own account which is set as admin but that made no difference.
      My Computer


  10. Posts : 46
    Windows 10
    Thread Starter
       #10

    I found setupact.log and this is the last part before the error:

    2017-10-25 12:26:29, Info TOOL Sysprep_Specialize_Bcd: Successfully specialized the bcd store. Status=[0x0]
    2017-10-25 12:26:29, Info SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Specialize_Bcd' from C:\Windows\System32\spbcd.dll without error
    2017-10-25 12:26:29, Info SYSPRP ActionPlatform::LaunchModule: Successfully executed 'SysPrepDtcSpecialize' from C:\Windows\system32\msdtcprx.dll without error
    2017-10-25 12:26:29, Info SYSPRP ActionPlatform::LaunchModule: Successfully executed 'SusRunOEMTask' from C:\Windows\System32\startupscan.dll without error
    2017-10-25 12:26:29, Error SYSPRP ActionPlatform::LaunchModule: Could not load DLL C:\Windows\System32\inetsrv\iissyspr.dll; dwRet = 0x7e[gle=0x0000007e]
    2017-10-25 12:26:29, Error SYSPRP SysprepSession::ExecuteAction: Failed during sysprepModule operation; dwRet = 0x7e[gle=0x0000007e]
    2017-10-25 12:26:29, Error SYSPRP SysprepSession::ExecuteInternal: Error in executing action for Microsoft-Windows-IIS-SharedLibraries; dwRet = 0x7e[gle=0x0000007e]
    2017-10-25 12:26:29, Error SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Specialize.xml; dwRet = 0x7e
    2017-10-25 12:26:29, Error SYSPRP RunPlatformActions:Failed while executing Sysprep session actions; dwRet = 0x7e
    2017-10-25 12:26:29, Info IBS Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers
    2017-10-25 12:26:29, Info IBS Callback_Specialize: Specialize return: [126]
    2017-10-25 12:26:29, Error [0x060435] IBS Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x7e
    2017-10-25 12:26:29, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not configure Windows to run on this computer's hardware.]
    Hope it means something to someone?

    Edit: So I just googled the final error "IBS Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x7e" and found this blog: [SOLVED] Windows Setup could not configure Windows on this computer’s hardware s Blog with two possible options so I'll try those for now.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:18.
Find Us




Windows 10 Forums