Update KB3000850 fails to install

Anonymous
2014-11-26T14:09:39+00:00

Hi there,

I have a problem installing update KB3000850. It downloads and appears to install OK until the computer restarts to complete the installation. It gets to about 8% of configuring windows updates and then I get the following message:

failure configuring windows

undoing changes

The computer restarts and is usable. I don't know a great deal about windows error reporting but I checked the C:\Windows\Logs\CBS\CBS log and found the following message:

CBS Failed installing driver updates [HRESULT - 0x80070003 - ERROR_PATH_NOT_FOUND]

I checked the Event Viewer and found the following message in the Windows Logs\System section:

Event ID: 7023

Source: Service Control Manager

The Windows Modules Installer service terminated with the following error:

The system cannot find the path specified.

I have no idea which path it cannot find. I have tried running the SFC and DISM commands and have tried the Windows Update Automated Troubleshooter but none of these seem to fix it. I understand there is a problem with the Avast anti-virus software but I am running Norton 360. I am using Classic Shell and am not sure if that is causing the problem but don't want to uninstall it if the error is being caused by something else.

Any help or advice would be most gratefully received.

Thanks in advance,

Richard

Windows for home | Previous Windows versions | 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

110 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2014-12-03T00:04:35+00:00

    2014-11-30 18:21:32, Info                  CBS    Not able to find package: Package_1_for_KB2889543~31bf3856ad364e35~amd64~~6.3.1.0 from the cached windows update index. [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    http://support.microsoft.com/kb/2889543

    <quote>

    Article ID: 2889543 - Last Review: September 24, 2013 - Revision: 2.0

    </quote>

    Why in the world are you being given such an obsolete update?  Did you try doing some kind of cleanup (which would have deleted or at least compressed WinSxS modules)?

    To try to find out the state of your Flash* modules please try the following Powershell pipeline.  Run it as Administrator: Windows Powershell (e.g. elevated) to try to minimize warning messages.

    PS C:\windows> **dir -Re -Fi "Flash*" ** **Sort-Object Name, CreationTime ** <br>ft Length, FullName -AutoSize

    Note that I am giving the actual command line including the prompt to give the directory level you should start it from.  Also, note that even when we specify -AutoSize that the output may be truncated depending on the window size, so please make sure that your window is big enough to capture the full path of the longest name.

    For some time I have had the opinion that updates misuse the module timestamp and the results from this output for my case are confirming this in spades.   So, I consider just the Length to be the most significant factor in what version a module is.  E.g. in particular where the System modules sort for CreationTime bears no resemblance to what version they actually are (according to their Length).  Otherwise I was expecting to see the System modules ordered after the SxS copy.  YMMV.

    Checking System Update Readiness.

    (p) CSI Payload Corrupt wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc\FlashPlayerApp.exe

    Repair failed: Missing replacement payload.

    (p) CSI Payload Corrupt wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc\FlashPlayerCPLApp.cpl

    Repair failed: Missing replacement payload.

    (p) CSI Payload Corrupt wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc\FlashUtil_ActiveX.dll

    Repair failed: Missing replacement payload.

    (p) CSI Payload Corrupt amd64_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.16384_none_4b24378dd07ed912*dssec.dat*

    Repair failed: Missing replacement payload.

    What is dssec.dat?  And again, why are you seeing reports about such ancient (16384) modules?  There is something fishy here.   Both system versions are the same length?  Neither appear in the SxS by those lengths?  Weirder still the version that you are having trouble with appears to have been archived recently (length 12 bytes but sorting just before the two system versions.)  But all the others appear compressed (length 8489) so we can't use this to check for version.  There is no FileVersion for a .dat file anyways and it looks as if LastWriteTime might be a better sort key.  Well, at least that gets the version "build" numbers into a logical order.  Otherwise the ordering is still inconsistent with my expectation.  YMMV

    PS C:\windows> dir -Re -Fi "dssec.dat" Sort-Object Name, LastWriteTime ft Length, FullName -AutoSize<br><br><br>Length FullName <br><br>------ -------- <br><br>215943 C:\windows\System32\dssec.dat <br><br>215943 C:\windows\SysWOW64\dssec.dat <br><br>    12 C:\windows\WinSxS\amd64_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.16384_none_4b24378dd07ed912\dssec.dat <br><br>    12 C:\windows\WinSxS\x86_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.16384_none_ef059c0a182167dc\dssec.dat <br><br>  8489 C:\windows\WinSxS\amd64_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.17415_none_4b70d269d045459a\dssec.dat <br><br>  8489 C:\windows\WinSxS\x86_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.17415_none_ef5236e617e7d464\dssec.dat

    HTH

    Robert

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-12-02T19:17:01+00:00

    Hi Robert,

    The part of the log that immediately precedes the earlier timestamp are as follows:

    2014-11-30 18:21:32, Info                  CBS    Not able to find package: Package_1_for_KB2889543~31bf3856ad364e35~amd64~~6.3.1.0 from the cached windows update index. [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    2014-11-30 18:21:32, Info                  CBS    Failed to find package: Package_1_for_KB2889543~31bf3856ad364e35~amd64~~6.3.1.0 from the index mapping [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    2014-11-30 18:21:32, Info                  CBS    Failed to get WU category/updateID for package: Package_1_for_KB2889543~31bf3856ad364e35~amd64~~6.3.1.0 [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    2014-11-30 18:21:32, Info                  CBS    Failed to get the mapping of package: Package_1_for_KB2889543~31bf3856ad364e35~amd64~~6.3.1.0, continue. [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    2014-11-30 18:21:32, Info                  CBS    Not able to find package: Microsoft-Windows-Client-Features-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~6.3.9600.16384 from the cached windows update index. [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    2014-11-30 18:21:32, Info                  CBS    This session already attempted mapping cache rebuild, skip.

    2014-11-30 18:21:32, Info                  CBS    Failed to find package: Microsoft-Windows-Client-Features-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~6.3.9600.16384 from the index with mapping index packages recently rebuilt,  [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    2014-11-30 18:21:32, Info                  CBS    Failed to get WU category/updateID for package: Microsoft-Windows-Client-Features-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~6.3.9600.16384 [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    2014-11-30 18:21:32, Info                  CBS    Failed to get the mapping of package: Microsoft-Windows-Client-Features-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~6.3.9600.16384, continue. [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    2014-11-30 18:21:32, Info                  CBS    Failed to find  [HRESULT = 0x800f090e - CBS_E_EMPTY_PACKAGE_MAPPING_INDEX]

    2014-11-30 18:21:32, Info                  CBS    Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]

    2014-11-30 18:21:32, Info                  CBS    Failed to repair store. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]

    2014-11-30 18:21:32, Info                  CBS    Ensure CBS corruption flag is clear

    2014-11-30 18:21:32, Info                  CBS    

    =================================

    Checking System Update Readiness.

    (p) CSI Payload Corrupt wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc\FlashPlayerApp.exe

    Repair failed: Missing replacement payload.

    (p) CSI Payload Corrupt wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc\FlashPlayerCPLApp.cpl

    Repair failed: Missing replacement payload.

    (p) CSI Payload Corrupt wow64_adobe-flash-for-windows_31bf3856ad364e35_6.3.9600.16407_none_270c708771a3c5dc\FlashUtil_ActiveX.dll

    Repair failed: Missing replacement payload.

    (p) CSI Payload Corrupt amd64_microsoft-windows-dssec_31bf3856ad364e35_6.3.9600.16384_none_4b24378dd07ed912\dssec.dat

    Repair failed: Missing replacement payload.

    Summary:

    Operation: Detect and Repair 

    Operation result: 0x800f0906

    Last Successful Step: Entire operation completes.

    Total Detected Corruption: 4

    CBS Manifest Corruption: 0

    CBS Metadata Corruption: 0

    CSI Manifest Corruption: 0

    CSI Metadata Corruption: 0

    CSI Payload Corruption: 4

    Total Repaired Corruption: 0

    CBS Manifest Repaired: 0

    CSI Manifest Repaired: 0

    CSI Payload Repaired: 0

    CSI Store Metadata refreshed: True

    Total Operation Time: 1078 seconds.

    2014-11-30 18:21:32, Info                  CBS    SQM: CheckSur: hrStatus: 0x800f0906 [CBS_E_DOWNLOAD_FAILURE], download Result: 0x800f0941 [CBS_E_WU_MAPPING_UNAVAILABLE]

    2014-11-30 18:21:32, Info                  CBS    Count of times corruption detected: 2

    2014-11-30 18:21:32, Info                  CBS    Seconds between initial corruption detections: -1

    2014-11-30 18:21:32, Info                  CBS    Seconds between corruption and repair: -1

    2014-11-30 18:21:33, Info                  CBS    SQM: Upload requested for report: CheckSurSqm, session id: 142858, sample type: Standard

    2014-11-30 18:21:33, Info                  CBS    SQM: Warning: Failed to get machine name. The data won't be available. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    2014-11-30 18:21:33, Info                  CBS    SQM: Warning: Failed to get domain name. The data won't be available. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    2014-11-30 18:21:33, Info                  CBS    SQM: Queued 1 file(s) for upload with pattern: C:\WINDOWS\servicing\sqm\CheckSurSqm_*_std.sqm, flags: 0x2

    2014-11-30 18:21:33, Info                  CBS    Failed to run Detect and repair. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]

    2014-11-30 18:21:33, Info                  CBS    SQM: Upload callback called with file path: C:\WINDOWS\servicing\sqm\CheckSurSqm_0_std.sqm, status: 0x0, HTTP response: 403

    Does this make any sense to you?

    Thanks again for your help with this.

    Regards,

    Richard

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-12-01T22:52:03+00:00

    2014-11-30 18:21:34, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30411975_4110630632 [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]

    Ok.  So, now the cause of that symptom will be before the place that you started your snip.  In particular, what was it trying to download that failed?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-12-01T20:03:31+00:00

    Hi Robert,

    Thanks for your reply. The entries in my CBS.log for that timestamp are as follows:

    2014-11-30 18:21:34, Info                  CBS    Reboot mark cleared

    2014-11-30 18:21:34, Info                  CBS    Winlogon: Deregistering for CreateSession notifications

    2014-11-30 18:21:34, Info                  CBS    Winlogon: Stopping notify server

    2014-11-30 18:21:34, Info                  CBS    Winlogon: Unloading SysNotify DLL

    2014-11-30 18:21:34, Info                  CBS    Exec: Processing complete, session(Corruption Repairing): 30411975_4110630632 [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]

    2014-11-30 18:21:34, Error                 CBS    Session: 30411975_4110630632 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]

    2014-11-30 18:21:34, Info                  CBS    Session: 30411975_4110630632 finalized. Download error: 0x800f0941 [CBS_E_WU_MAPPING_UNAVAILABLE], Reboot required: no [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]

    2014-11-30 18:21:34, Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x800f0906]

    2014-11-30 18:23:34, Info                  CBS    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

    2014-11-30 18:23:34, Info                  CBS    TiWorker signaled for shutdown, going to exit.

    2014-11-30 18:23:34, Info                  CBS    Ending the TiWorker main loop.

    2014-11-30 18:23:34, Info                  CBS    Starting TiWorker finalization.

    2014-11-30 18:23:34, Info                  CBS    Ending the TrustedInstaller main loop.

    2014-11-30 18:23:34, Info                  CBS    Starting TrustedInstaller finalization.

    2014-11-30 18:23:34, Info                  CBS    Ending TrustedInstaller finalization.

    2014-11-30 18:23:34, Info                  CBS    Ending TiWorker finalization.

    So, it appears 0x800f0906 - CBS_E_DOWNLOAD_FALIURE is causing the DISM failure problem. Again, I've no idea what is causing this. Any ideas?

    Thanks for your help with this.

    Regards,

    Richard

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-11-30T19:15:19+00:00

    Hi Robert,

    Thanks for your help, I renamed the DISM log and in the one that was created I found the following warnings and errors:

    014-11-30 18:03:33, Warning               DISM   DISM Provider Store: PID=4244 TID=4720 Failed to Load the provider: C:\Users\user\AppData\Local\Temp\468A5595-934F-42F5-862A-60AE1302BCC6\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2014-11-30 18:03:34, Warning               DISM   DISM Provider Store: PID=4244 TID=4720 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)

    2014-11-30 18:03:34, Warning               DISM   DISM Provider Store: PID=4244 TID=4720 Failed to Load the provider: C:\Users\user\AppData\Local\Temp\468A5595-934F-42F5-862A-60AE1302BCC6\Wow64provider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)

    2014-11-30 18:03:34, Warning               DISM   DISM Provider Store: PID=4244 TID=4720 Failed to Load the provider: C:\Users\user\AppData\Local\Temp\468A5595-934F-42F5-862A-60AE1302BCC6\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2014-11-30 18:21:34, Error                 DISM   DISM Package Manager: PID=4244 TID=4720 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0906)

    2014-11-30 18:21:34, Error                 DISM   DISM Package Manager: PID=4244 TID=4720 The source files could not be found and download failed. Their location can be specified using the /source option to restore the feature. - GetCbsErrorMsg

    2014-11-30 18:21:34, Error                 DISM   DISM Package Manager: PID=4244 TID=4720 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0906)

    2014-11-30 18:21:34, Error                 DISM   DISM Package Manager: PID=4244 TID=4720 The source files could not be found and download failed. Their location can be specified using the /source option to restore the feature. - GetCbsErrorMsg

    2014-11-30 18:21:34, Error                 DISM   DISM Package Manager: PID=4244 TID=4720 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f0906)

    2014-11-30 18:21:34, Error                 DISM   DISM Package Manager: PID=4244 TID=4720 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0906)

    None of that makes much sense to me.

    Richard

    Was this answer helpful?

    0 comments