none
Win10 Creators Update Fail – Error 8007007e RRS feed

  • Question

  • Win10 Creators Update Fail – Error 8007007e
    Current version Win10 Version 10.0.14393

    I’ve had no issues with the PC and updates have always worked

    (TIA for any help, but if your suggestion is to re-install Win10, that is not helpful. I just did a complete reinstall when I went from Win7 to Win10 last year)

    • Uninstalled 3rd party AV/AM 
    • Downloading the full Creators Update install fails with same error 8007007e
    • Tried this – didn’t help: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-creator-update-fails-with-error/5ead5df7-7116-4e6a-861f-0538a870da1f
    • Ran a full checkdsk on boot – no errors
    • SFC /scannow fails with “Windows Resource Protection could not start the repair service.”
    • Tried a few hundred Google finds for that error – nothing works (yes, Trusted Installer is running)
    • Booted to Win RE Command Line – SFC same results using offbootdir offwindir
    • Running under Win RE – SFC does run against the RE environment fine. Point it to the installed Win10 and get “Windows Resource Protection could not start the repair service”?
    • dism /online /cleanup-image /scanhealth  – Error: 0x8000ffff DISM failed. No operation was performed.
    • dism /online /cleanup-image /checkhealth - No component store corruption detected. The operation completed successfully.
    • dism /online /cleanup-image /restorehealth fail - Error: 0x8000ffff DISM failed. No operation was performed.
    • dism /online /cleanup-image /restorehealth /source:wim:F:\sources\install.wim:1 /limitaccess failed - Error: 0x8000ffff (source was correct and same version)
    • Reset Windows Update Components: https://support.microsoft.com/en-us/help/971058/how-do-i-reset-windows-update-components
    • Running the tool gives an error that there is a pending reboot required. Yet it does not matter how often it is rebooted – same message (even after clearing the updates folder in the first step above and more Google finds - nothing)

    Also ran a full Tweaking.com Windows Repair.

    Relevant (maybe) log entries:

    DISM Package Manager: PID=4444 TID=17592 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    DISM Package Manager: PID=4444 TID=17592 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize
    DISM Package Manager: PID=4444 TID=13424  Error in operation: (null) (CBS HRESULT=0x8000ffff) - CCbsConUIHandler::Error
    DISM Package Manager: PID=4444 TID=17592 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x8000ffff)
    DISM Package Manager: PID=4444 TID=17592 Failed processing package changes with session option CbsSessionOptionDetectStoreCorruption - CDISMPackageManager::ScanHealth(hr:0x8000ffff)
    DISM Package Manager: PID=4444 TID=17592 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x8000ffff)

    A number of these hash file issues

     Found: {l:32 +8E2LWXm13aJi3V9kqt9/7kc21gy8Oe3ASYNqwm/JeA=} Expected: {l:32 KMZp+72oqlEq+k8c+GfZKpL77mxe7V9f3r+ckCRz+Sg=}
      CSI    0000012b Hashes for file member \SystemRoot\WinSxS\amd64_wvpci.inf_31bf3856ad364e35_10.0.14393.0_none_aacb40b5fb9d2a41\wvpci.inf do not match actual file [l:9]'wvpci.inf' :
      Found: {l:32 8OtIRB283Y0zv477xNEuTpS2AAyxHULxv3DK6FrIegg=} Expected: {l:32 w9JlnAW34qW6RrI247dOaoF4GCNsnCk9FurvxAza1SM=}
      CSI    0000012c Hashes for file member \SystemRoot\WinSxS\amd64_wvpci.inf_31bf3856ad364e35_10.0.14393.0_none_aacb40b5fb9d2a41\vpci.sys do not match actual file [l:8]'vpci.sys' :
      Found: {l:32 HxhhBULZU72bUaN5IinCP6sUAYB7yCsOLNSZu1Sqgfw=} Expected: {l:32 jJJ1XdtBrX3aFkPX8y+qD8p+LGXGlhHrXsGzJ26o28c=}
      CSI    0000012d Hashes for file member \SystemRoot\WinSxS\amd64_wvpcivsp.inf_31bf3856ad364e35_10.0.14393.0_none_ac36379bf64c7734\vpcivsp.sys do not match actual file [l:11]'vpcivsp.sys' :
      Found: {l:32 Lx1INN/IMMM9HsGmHA8Y1b+yvBsQa4VsMAK/QzqSf0s=} Expected: {l:32 fJIqnGN+ZgzOZklHJGTk9a514/Cq7aDeqVI6A36Ffj4=}
      CSI    0000012e Hashes for file member \SystemRoot\WinSxS\amd64_wvpcivsp.inf_31bf3856ad364e35_10.0.14393.0_none_ac36379bf64c7734\wvpcivsp.inf do not match actual file [l:12]'wvpcivsp.inf' :
      Found: {l:32 hoVPfFAWPWdGoXCvM3aBoa6+Mm2aWnZw3uaddfhOJq4=} Expected: {l:32 tPSpQM6AAop3fWZHiBXZtIkq28jbAwHK7rcItFz2ut8=}

     

    And

      CBS    Current tick count lower than last tick count. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
      CSI    00000130@2017/6/22:14:30:31.271 CSI Transaction @0x1be3f3f66a0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI5.30600035_4240924865:1/'
      CSI    00000133@2017/6/22:14:30:31.272 (F) onecore\base\wcp\componentstore\com\store.cpp(4765): Error E_UNEXPECTED originated in function Windows::COM::CComponentStore::InternalTransact expression: ((HRESULT)0x8000FFFFL)
    [gle=0x80004005]
      CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
      CBS    Added C:\Windows\Logs\CBS\CbsPersist_20170622122543.log to WER report.
      CBS    Added C:\Windows\Logs\CBS\CbsPersist_20170620221901.log to WER report.
      CBS    Added C:\Windows\Logs\CBS\CbsPersist_20170619130039.log to WER report.
      CBS    Added C:\Windows\Logs\CBS\CbsPersist_20170618184444.log to WER report.
      CBS    Not able to add current session file to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
      CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
      CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
      CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
      CSI    00000134 (F) E_UNEXPECTED #1257368# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_Analyze(Flags = 0, riid = {f4d9decb-0250-4ad4-9500-85c7f2f281ec}, ppUnk = NULL, disp = 0)[gle=0x8000ffff]
      CBS    Failed to get transaction analysis. [HRESULT = 0x8000ffff - E_UNEXPECTED]
      CBS    Failed to get inventory. [HRESULT = 0x8000ffff - E_UNEXPECTED]
      CSI    00000135@2017/6/22:14:30:31.292 CSI Transaction @0x1be3f3f66a0 destroyed
      CBS    Failed to get CSI inventory [HRESULT = 0x8000ffff - E_UNEXPECTED]
      CBS    Not able to get CBS component onwers for component amd64_microsoft-windows-security-credssp_31bf3856ad364e35_10.0.14393.447_none_fd9232e83f78a285 [HRESULT = 0x8000ffff - E_UNEXPECTED]
      CBS    Failed to create a new corrupted component entry. [HRESULT = 0x8000ffff - E_UNEXPECTED]
      CBS    Failed to check CSI store. [HRESULT = 0x8000ffff - E_UNEXPECTED]

     
    Any help (beyond reinstall) is appreciated!
    Thursday, June 22, 2017 6:05 PM

Answers

  • I just received the push for W10 CU (1703) last night. I let it run and this morning logged into W10 CU just fine. All seems to be working, sfc is still clean. So here is what I know:

    1. Everything was fine in May, as I ended up restoring to early May
    2. sfc did show a repair after the restore to May (something about speech recognition)
    3. However, sfc ran just fine as did dism from that May restore
    4. Prior to restoring to May - everything above was going on, no sfc, dism and no restore point
    5. This allowed me to go to a May restore point: http://borncity.com/win/2017/03/02/windows-10-update-kb3213986-kills-system-restore/
    6. The restore point didn't help
    7. Doing an image restore from a May backup and then applying the cumulative updates - then allowing W10 CU to come down on its own worked
    8. sfc, dism and all the new features are working fine

    I'm guessing something bad happened during the W10 CU "upgrade" when I ran it manually. Again noting http://gadgets.ndtv.com/laptops/news/windows-10-creators-update-shouldnt-be-installed-manually-warns-microsoft-1686594

    It may have nothing to do with that or I may have received the W10CU rollups/changes via the push that I didn't get manually kicking it off. At any rate, thank God for backups and thank you for your help!

    Saturday, July 1, 2017 4:01 PM

All replies

  • • Uninstalled 3rd party AV/AM 

    Looks like something is still there interfering.  See if the manufacturer has a cleanup program to supplement a broken uninstaller.


    Robert Aldwinckle
    ---

    Thursday, June 22, 2017 7:13 PM
  • I just download their removal tool - no joy. Actually since, for example, sfc would not run under the Windows Recovery Environment - I doubt it has anything to do with any 3rd party program. But it was worth a try - thanks. I am running out of ideas.
    Thursday, June 22, 2017 10:55 PM
  • Looks like something is still there interfering.

    I should have paid closer attention to what was being reported corrupted.  It looks like it is Hyper-V.  My nemesis. The number of times I have had to uninstall an update and then uninstall Hyper-V in order to get a clean install of these cumulative updates defies belief. It started with the previews long ago and now has leaked into the production version.


    Robert Aldwinckle
    ---

    Friday, June 23, 2017 1:48 AM
  • More bad news for me. I went to disable/remove Hyper-V and it is not installed.
    Friday, June 23, 2017 12:17 PM
  • So I thought I'd try manual updates up to Creators.

    I'm running Win 10 Pro, 1607, 14939.1198

    I go to the Win10 Update History and see:

    Windows 10 Version 1607 and Windows Server 2016
    KB4022715 (OS Build 14393.1358)
    KB4023680 (OS Build 14393.1230)
    KB4019472 (OS Build 14393.1198)

    I then go to the Update Site and grab KB4023680 which should be the next update for 14393.1198:

    2017-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4023680)

    But when I try to run it I get "The update is not applicable to your computer"

    Am I missing something?

    Friday, June 23, 2017 1:05 PM
  • Am I missing something?

    Try using  PowerShell  Get-WindowsUpdateLog  to try to find out what is being detected.  One possibility is that you have something installed but not applied.  Hopefully it won't be necessary to invoke verbose logging to get enough information about the detection but that is an option.

    Also to try to understand that virtual driver symptom better you could look at what you have for it using PowerShell.

    PS>gl
    Path
    ----
    C:\WINDOWS
    
    PS>LS -Re -Filt *vpci*.sys -Fo -EA:SilentlyContinue | sort LastWriteTime | ft LastWriteTime, Length, FullName -AutoSize -Wrap | out-string -Width 80

    E.g. find out what's installed and what's applied.  FWIW when I do that I see vpci.sys is applied but that I also have a (much smaller) vpcivsp.sys which I got recently which is not.  Currently I am running without Hyper-V.  Unfortunately I can't say what the significance of the last date might be.  E.g. it might be when I uninstalled Hyper-V but I do not know for sure.  I may try installing Hyper-V again and check for differences while this is fresh in my mind.



    Robert Aldwinckle
    ---

    Friday, June 23, 2017 3:01 PM
  • Not really seeing much in the log to react to. I have fallen back to now trying to see why I can't DISM fix. I first tried to fall back to a system restore point back in May - after a long time, that failed and came back to the current state.

    I did manage to fix the reset update components - no longer get the pending restart issue. But that didn't fix anything as far as I can tell.

    So in normal, safe and RE mode - I can not get anything from SFC nor DISM to work.

    Here are the results in safe mode of a Dism /Online /Cleanup-Image /ScanHealth

    (Offline also fails with the same error)

    Any thoughts on Error in operation: (null) (CBS HRESULT=0x8000ffff) - CCbsConUIHandler::Error ?

    DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
    DISM   DISM Provider Store: PID=1340 TID=3372 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
    DISM   DISM Provider Store: PID=1340 TID=3372 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
    DISM   DISM Package Manager: PID=1340 TID=3372 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    DISM   DISM Package Manager: PID=1340 TID=3372 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    DISM   DISM Package Manager: PID=1340 TID=3372 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    DISM   DISM Package Manager: PID=1340 TID=3372 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize
    DISM   DISM Package Manager: PID=1340 TID=3168  Error in operation: (null) (CBS HRESULT=0x8000ffff) - CCbsConUIHandler::Error
    DISM   DISM Package Manager: PID=1340 TID=3372 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x8000ffff)
    DISM   DISM Package Manager: PID=1340 TID=3372 Failed processing package changes with session option CbsSessionOptionDetectStoreCorruption - CDISMPackageManager::ScanHealth(hr:0x8000ffff)
    DISM   DISM Package Manager: PID=1340 TID=3372 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x8000ffff)
    DISM   DISM Package Manager: PID=1340 TID=3372 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x8000ffff)
    DISM   DISM Package Manager: PID=1340 TID=3372 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=8000FFFF
    DISM   DISM Provider Store: PID=1340 TID=3372 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    DISM   DISM Provider Store: PID=1340 TID=3372 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    DISM   DISM Provider Store: PID=1340 TID=3372 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    DISM   DISM Provider Store: PID=1340 TID=3372 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    DISM   DISM Package Manager: PID=1340 TID=3372 Finalizing CBS core. - CDISMPackageManager::Finalize

    Saturday, June 24, 2017 4:47 PM
  • may try installing Hyper-V again and check for differences

    a bigger vpcivsp.sys is now applied to the OS.  I wasn't expecting a change of size but I guess it makes sense.


    Robert Aldwinckle
    ---

    Saturday, June 24, 2017 10:09 PM
  • Well Robert, I think you are on to something based on more research. I thought I'd just roll back from the last two rollups and try to jump to Creators. However, I could not  - restores kept failing with 80070091. It appears this is Microsoft induced based on this blog and associated linked articles (re: kb321986) http://borncity.com/win/2017/03/02/windows-10-update-kb3213986-kills-system-restore/

    (of note in the above link "January 2017 update KB3213986 mentions also fixes in Hyper-V and App-V")

    Using Quenni's linked articles and modifying the batch file to match my OfficeHub WindowsApps entries allowed me to delete those folders and the restore point worked. Yet, I still cannot update to Creators and keep getting 8007007e. I also can't install anything from windows features (Telnet / Hyper-V) - all fail with 80073701.

    I was thinking I must have something really wrong with my system since I could not do a restore point. Finding the issues with kb321986 and realizing uninstalling that KB doesn't even fix the issue, you have to manually remove specific folders (officehub) from system folder WindowsApps - tells me a lot.

    I'm still digging but it appears to me I am battling more Microsoft updates and less system corruption!

     

    Sunday, June 25, 2017 10:23 AM
  • Well this is getting sad. I was able to roll back to a May cumulative but still cannot install any rollups, they all give the 8007007e. I tried the stand alone 1703 - same error. I cannot run sfc nor dism to /restorehealth - pretty much everything in the OP. So I decided to try an in-place upgrade to 1703. That too failed (albeit I didn't get an error code and was not able to find a log to review). The system seems fine, no other issues. I'm stuck in limbo. I read others cleared up a number of problems (including sfc) after getting to 1703. I just can't seem to get there.

    Monday, June 26, 2017 12:23 PM
  • Well - for the record, I have restored to an early May backup. sfc and dism both work. sfc came back with a repair, looked like only speech recognition was repaired. Second run sfc came back clean, so too with dism. We will see what happens when I pull updates.
    Wednesday, June 28, 2017 12:58 AM
  • This may have been my issue - http://gadgets.ndtv.com/laptops/news/windows-10-creators-update-shouldnt-be-installed-manually-warns-microsoft-1686594

    I took the Get it Now from Windows update. It said "Good News... Get it now". I did and that may be a big mistake. I'll side with the article and wait for it to be pushed.

    Wednesday, June 28, 2017 1:47 PM
  • Get it now". I did and that may be a big mistake.

    What was the result?  An abort?  Previously you indicated you had a clean system (in terms of SFC and DISM scans), so if you can't install it may be an indication of an interferer or a new compatibility issue.  Then the best you could expect from anything else would be a clearer indication of why there was one.  Typically they don't even acknowledge that that is what they are doing.

    There is a feature called "compatibility scan".  Perhaps you should try it instead.

    https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-pre-upgrade-validation-using-setup-exe/ 

    <quote>

    a command line switch that tells it to “check for compatibility” but not actually perform the upgrade. 
    </quote>

    Note that going from W10 AU to W10 CU could be considered an "upgrade" and not just an "update".



    Robert Aldwinckle
    ---

    Wednesday, June 28, 2017 8:00 PM
  • I just received the push for W10 CU (1703) last night. I let it run and this morning logged into W10 CU just fine. All seems to be working, sfc is still clean. So here is what I know:

    1. Everything was fine in May, as I ended up restoring to early May
    2. sfc did show a repair after the restore to May (something about speech recognition)
    3. However, sfc ran just fine as did dism from that May restore
    4. Prior to restoring to May - everything above was going on, no sfc, dism and no restore point
    5. This allowed me to go to a May restore point: http://borncity.com/win/2017/03/02/windows-10-update-kb3213986-kills-system-restore/
    6. The restore point didn't help
    7. Doing an image restore from a May backup and then applying the cumulative updates - then allowing W10 CU to come down on its own worked
    8. sfc, dism and all the new features are working fine

    I'm guessing something bad happened during the W10 CU "upgrade" when I ran it manually. Again noting http://gadgets.ndtv.com/laptops/news/windows-10-creators-update-shouldnt-be-installed-manually-warns-microsoft-1686594

    It may have nothing to do with that or I may have received the W10CU rollups/changes via the push that I didn't get manually kicking it off. At any rate, thank God for backups and thank you for your help!

    Saturday, July 1, 2017 4:01 PM