DISM log can be viewed at the One Drive link:
And, can you explain to me how to follow this instruction: "download an .msu file, extract its contents and then you could point DISM at that for its /source: operand. "
Thanks
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This error may appear anytime a Windows Update fails. To investigate possible solutions, we need to start with the specific error code.
We can do this by viewing your update history.
View failed update error code.
Please post here with your error code, so that the Community can try to help guide you appropriately.
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.
DISM log can be viewed at the One Drive link:
And, can you explain to me how to follow this instruction: "download an .msu file, extract its contents and then you could point DISM at that for its /source: operand. "
Thanks
Again, the instructions are over my head. I was born in 1956 and have a history degree. But I am trying, and appreciate the help.
I read the material from the link you provided, used the Deployment Image Servicing and Management (DISM) tool, and got this result:
C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
C:\WINDOWS\system32>
Now, I need to figure out how to follow this instruction: "download an .msu file, extract its contents and then you could point DISM at that for its /source: operand. "
What should I do with C:\Windows\Logs\CBS\CBS.log?
Some are uploading it to their OneDrive in a Public folder and then pasting a link to that. However, if you went back to that link I gave you would see some patterns in it that you could search for. For example, I think seeing the Summary of the Repair attempt and the list of things that DISM found broken could be useful.
2015-03-04 10:32:10, Info CBS WER: Generating failure report for package: Package_for_KB3021953~31bf3856ad364e35~amd64~~6.3.1.0, status: 0x80073712, failure source:
03-03 16:46:21, Error DISM DISM Package Manager: PID=7984 TID=4100 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f) 2015-03-03 16:46:21, Info DISM DISM Package Manager: PID=7984 TID=4100 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log -
This shows that the DISM log and CBS log snippets are not synchronized. E.g. according to DISM you apparently did a Cleanup-Image on the 3rd. That's where you should be looking in the CBS.log. In fact, by now it may have split into an archived piece that you would have to search in or upload instead.
However, the piece of CBS.log that you captured does demonstrate some useful information that you could use on a different tack. E.g. that package name could be used to download an .msu file, extract its contents and then you could point DISM at that for its /source: operand. That is the insight that the thread I pointed you to gave me. Previously descriptions about /source: such as this and the things it links to were less clear about what it could be.
C.f.
https://support.microsoft.com/kb/947821?wa=wsignin1.0
FYI
Robert
C:\Windows\Logs\CBS\CBS.log contains the log of the sfc command.
What should I do with C:\Windows\Logs\CBS\CBS.log? I tried going to that address and did not understand the info that came up. Should I paste in in here for community help? It is a lot of info, and if I pasted it here, it would take up a huge amount of space. Here is a small sample of some "fail" messages within this large page:
2015-03-04 10:32:10, Error CSI 0000000b (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #2099# from CCSDirectTransaction::OperateEnding at index 0 of 2 operations, disposition 0[gle=0xd015001a]
2015-03-04 10:32:10, Error CSI 0000000c (F) HRESULT_FROM_WIN32(14098) #1926# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddComponents(Flags = 4, a = @0x43dece0840, mp = @0x43dece1040, disp = 0)[gle=0x80073712]
2015-03-04 10:32:10, Info CBS Failed to add one or more component [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-03-04 10:32:10, Error CBS Failed to complete component closure [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-03-04 10:32:10, Info CBS CommitPackagesState: Started persisting state of packages
2015-03-04 10:32:10, Info CBS CommitPackagesState: Completed persisting state of packages
2015-03-04 10:32:10, Info CSI 0000000d@2015/3/4:16:32:10.505 CSI Transaction @0x43ddb080c0 destroyed
2015-03-04 10:32:10, Info CBS Perf: Resolve chain complete.
2015-03-04 10:32:10, Info CBS Exec: Store corruption found during execution, but auto repair is already attempted today, skip it.
2015-03-04 10:32:10, Info CBS Failed to resolve execution chain. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-03-04 10:32:10, Error CBS Failed to process single phase execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-03-04 10:32:10, Info CBS WER: Generating failure report for package: Package_for_KB3021953~31bf3856ad364e35~amd64~~6.3.1.0, status: 0x80073712, failure source: Resolve, start state: Absent, target state: Staged, client id: WindowsUpdateAgent
I have seen reports of issues with CNBJ2530.DPB on multiple computers but these were not relevant to the problems I was experiencing and were fixed by dism /restorehealth
There may be some information in C:\WINDOWS\Logs\DISM\dism.log as to why the dism command is failing.
Should I paste in in here for community help? It is a lot of info as well. Again, small sample:
2015-03-03 16:46:21, Info DISM DISM Package Manager: PID=7984 TID=6656 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
2015-03-03 16:46:21, Error DISM DISM Package Manager: PID=7984 TID=4100 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2015-03-03 16:46:21, Error DISM DISM Package Manager: PID=7984 TID=4100 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2015-03-03 16:46:21, Error DISM DISM Package Manager: PID=7984 TID=4100 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2015-03-03 16:46:21, Error DISM DISM Package Manager: PID=7984 TID=4100 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2015-03-03 16:46:21, Error DISM DISM Package Manager: PID=7984 TID=4100 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
2015-03-03 16:46:21, Error DISM DISM Package Manager: PID=7984 TID=4100 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2015-03-03 16:46:21, Info DISM DISM Package Manager: PID=7984 TID=4100 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2015-03-03 16:46:21, Info DISM DISM Provider Store: PID=7984 TID=4100 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-03-03 16:46:21, Info DISM DISM Provider Store: PID=7984 TID=4100 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-03-03 16:46:21, Info DISM DISM Provider Store: PID=7984 TID=4100 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2015-03-03 16:46:21, Info DISM DISM Provider Store: PID=7984 TID=4100 Finalizing the servicing provider(DISM Package Manager) -
I have not had to use the /source option which appears to be useful if you have access to a valid Windows image.
I guess I don't, since I don't know what a valid Windows image is. I bought the laptop -- a late model Lenovo Twist -- (no viruses) pre-loaded with Windows 8 and downloaded 8.1 from the Microsoft website. I do not have any disks or product keys. I though dism downloaded any corrupted/missing packages.
Could there been a problem with Windows Update accessing the Microsoft servers? That might also explain why the download of the IE Flash fix is stalling at 5%. No, I don't think so. I have excellent wifi coverage in my house and can access anything I want on the internet. I can stream videos and do other things that require a good connection.
Thanks for the ongoing attempts to help me out here.
@showmethefacts, C:\Windows\Logs\CBS\CBS.log contains the log of the sfc command. I have seen reports of issues with CNBJ2530.DPB on multiple computers but these were not relevant to the problems I was experiencing and were fixed by dism /restorehealth
There may be some information in C:\WINDOWS\Logs\DISM\dism.log as to why the dism command is failing. I have not had to use the /source option which appears to be useful if you have access to a valid Windows image. I though dism downloaded any corrupted/missing packages.
Could there been a problem with Windows Update accessing the Microsoft servers? That might also explain why the download of the IE Flash fix is stalling at 5%.