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

....then you ran into other problems!

Hello Everyone.

I was experiencing (more severe version of) this problem too, thankfully was able to fix it today.

Below are the steps to follow.

1. Search for "View Local Services". Then open it.
2. Find Windows Updates there. Open it.
3. Default services statues there should be "Running". Click Stop to stop it.
4. Go to the disk that windows installed (Disk C usually). 
5. Find Windows folder there. Open it.
6. Find Software distribution folder. Open it and Delete all the folders inside it.

      Note: You will not able to delete all the folders if you do not stop service status.

7. Go to recycle bin and delete everything from there.
8. Follow steps 1 and 2. This time change the status to start.
9. Check for updates, install them, when windows asks for restart, restart it.  All the updates should finish without a problem.

You may also find this thread useful, which was between me and one of the experienced MVP's.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-we-couldnt-complete-the-updates-undoing/897ce4ca-7887-4c65-8639-46c71186a1de?page=2

Good luck!

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. "

Only partially.  That was SuWii's trick.  So all the details that are available are in that thread.

However, I can give you some hints based on that PackageName that you showed us--as an example.  We don't know yet if this is really your problem.

I like using PowerShell but the same functionality is available using DISM in a cmd window.

So, here's a cmdlet which shows what we can glean from that PackageName

One of the lines of its output is a link to

http://support.microsoft.com/?kbid=3021953

And in there are some download links for some .msu files.  You just need to pick the one which applies to your OS, download it and save it.

Now things get murky.  I have never done this before but from other blogs for other procedures supposedly once you have an .msu you can expand it and save the expansion.  My understanding is that all you would need to do then is point the /source:  operand at that.

The clearest procedure that I have seen was done for a different DISM command but hopefully the same technique would apply to the one that you would want to try.

http://blogs.technet.com/b/askcore/archive/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-within-windows.aspx

(Google search for

    dism expand .msu package

)

The reason that this won't be documented will be that by design it should not be necessary.  E.g. DISM is supposed to be all knowing and all powerful.  It is supposed to know what is needed to repair corruption, download it and install it, all without any operator intervention.  When you see the /Source: and /LimitAccess parameters documented they are never mentioned in terms of trying to work around a defect in DISM but only in terms of being used for a particular use-case such as bypassing a customer's update server.

BTW I worked with another poster who was having trouble with KB3000850 and Flash stuff turned out to be a red herring.

http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/update-kb3000850-fails-to-install/43125206-f39e-477f-b5b6-73a177abb589?page=4

FYI

Robert

@Robert Aldwinckle on forums, I did a search on 0x800f081f which first appears on 2015-03-03 16:46:21.  I compared the DISM log with one I created - I see the same first four lines below but I progress to "Staring corruption detect/repair info".

2015-03-03 10:58:06, Info                  DISM   DISM Provider Store: PID=4532 TID=12660 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider

2015-03-03 10:58:06, Info                  DISM   DISM Provider Store: PID=4532 TID=12660 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider

2015-03-03 10:58:06, Info                  DISM   DISM Package Manager: PID=4532 TID=12660 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine

2015-03-03 10:58:06, Info                  DISM   DISM Package Manager: PID=4532 TID=12660 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

2015-03-03 10:58:06, Info                  DISM   DISM Package Manager: PID=4532 TID=12660 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

2015-03-03 10:58:06, Info                  DISM   DISM Package Manager: PID=4532 TID=12660 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize

2015-03-03 11:36:52, Info                  DISM   DISM Package Manager: PID=4532 TID=12660  - CDISMPackageManager::Internal_Finalize

2015-03-03 11:36:52, Info                  DISM   DISM Package Manager: PID=4532 TID=12660 <----- Starting corruption detect/repair info -----> - CDISMPackageManager::Internal_Finalize

2015-03-03 11:36:52, Info                  DISM   DISM Package Manager: PID=4532 TID=12660  - CDISMPackageManager::Internal_Finalize

The failing log throws an error in the fifth line.  

2015-03-03 16:41:07, Info                  DISM   DISM Package Manager: PID=7984 TID=4100 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine

2015-03-03 16:41:07, Info                  DISM   DISM Package Manager: PID=7984 TID=4100 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

2015-03-03 16:41:07, Info                  DISM   DISM Package Manager: PID=7984 TID=4100 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

2015-03-03 16:41:07, Info                  DISM   DISM Package Manager: PID=7984 TID=4100 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize

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

The DISM log does not indicate what it is looking for.  Maybe the CBS log does.I found a post at http://geekswithblogs.net/Plumbersmate/archive/2014/09/29/windows-8ndashcanrsquot-install-.net-framework-3.5-0x800f0906-0x800f081f.aspx that talked about similar symptoms and showing some of the diagnostic steps.  I am not suggesting this is a NET 3.5 issue but the post does reference going to the CBS log to narrow down what source file is missing.  

@showmethefacts, if you can upload the CBS.log file to OneDrive, I can have a quick look at it.  This is well beyond my expertise but have an interest in learning more based on the horrible experience trying to get KB2919355 installed.

DISM log can be viewed at the One Drive link:

2015-03-05 08:19:08, Error                 DISM   DISM Package Manager: PID=7692 TID=7824 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0906)

Now find the section of the CBS.log where that was happening.   Since this was an error report the actual error would have occurred earlier but only by seconds--although I suppose it is conceivable that you might see it with a timestamp from the 08:18 minute range.

What you can look for also is the same  Checking System Update Readiness.  section as SuWii found.  There are no timestamps on those records but the timestamped record above it would be regarded as their timestamp.

Here is that thread again in RSS feed form.  In order to find examples of the DISM report in the CBS.log use the Displaying: filter to just show posts with  Checking  in them.

http://answers.microsoft.com/en-us/feed/t/2b0ed3e1-1835-4517-97dd-0a7abb6ef74c