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. Swipe in from the right edge of the screen (or, if you're using a mouse, pointing to the lower-right corner of the screen and moving the mouse pointer up), and tap or click Settings . Tap or click Change PC settings , and then Update and recovery . Tap or click View 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.

That is the link to the log after running the cmd command again about RestoreHealth Yes. That's just your entire DISM.log. I want to see the CBS.log related to the same event. 2015-03-09 20:40:25, Info DISM DISM Package Manager: PID=6076 TID=7992 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

https://onedrive.live.com/redir?resid=F56F7AEBD0068A0B!759&authkey=!AGWuBzcl_oefk7k&ithint=file%2cpdf That is the link to the log after running the cmd command again about RestoreHealth Thanks and let me know if you wanted something different

@ SMTF Are you going to upload your CBS.log related to your DISM cleanup-image request? Note that by now 2015-03-05 08:19 is probably no longer found in the CBS.log per se but you may still be able to find it in the one of the archived bits of it. Otherwise just do another request and upload its report from the CBS.log. HTH Robert

Dear Dyer, It is nice to see you here too. The problem that u mention was exist at the same time with the update issue, so it didnt start after i performed the steps above. IMHO, they are not related problems.

Robert and others, Should I try this? It's a completely different tack than anything suggested so far. And if I do try it, how do I do this: Go to the disk that windows installed (Disk C usually) Where does one "go to the disk that windows installed"?

Error: We couldn’t complete the updates, Undoing changes. Don’t turn off your computer.

Anonymous

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.

Swipe in from the right edge of the screen (or, if you're using a mouse, pointing to the lower-right corner of the screen and moving the mouse pointer up), and tap or click Settings.
Tap or click Change PC settings, and then Update and recovery.
Tap or click View 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.

0 comments

998 answers

Anonymous

That is the link to the log after running the cmd command again about RestoreHealth

Yes. That's just your entire DISM.log. I want to see the CBS.log related to the same event.

2015-03-09 20:40:25, Info DISM DISM Package Manager: PID=6076 TID=7992 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

0 comments

Anonymous

2015-03-10T01:53:22+00:00

https://onedrive.live.com/redir?resid=F56F7AEBD0068A0B!759&authkey=!AGWuBzcl_oefk7k&ithint=file%2cpdf

That is the link to the log after running the cmd command again about RestoreHealth

Thanks and let me know if you wanted something different
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-08T19:35:01+00:00

@ SMTF

Are you going to upload your CBS.log related to your DISM cleanup-image request?

Note that by now 2015-03-05 08:19 is probably no longer found in the CBS.log per se but you may still be able to find it in the one of the archived bits of it. Otherwise just do another request and upload its report from the CBS.log.

HTH

Robert
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-07T23:22:45+00:00

Dear Dyer,

It is nice to see you here too.

The problem that u mention was exist at the same time with the update issue, so it didnt start after i performed the steps above. IMHO, they are not related problems.
Was this answer helpful?

0 comments No comments
Anonymous

2015-03-07T16:55:44+00:00

Robert and others,

Should I try this? It's a completely different tack than anything suggested so far. And if I do try it, how do I do this:

Go to the disk that windows installed (Disk C usually)

Where does one "go to the disk that windows installed"?
Was this answer helpful?

0 comments No comments