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.

you would need to provide step by step instructions. No. It is too speculative. It's just an idea for someone who does know what I mean and wants to try it. It's really more about exploring the scope of what we can do with DISM than anything positive that I know about or even have high hopes for. I may try this myself if I get a virtual machine set up to do it to.

"...My partition size is 334 GB with 192GB free, so space is definitely NOT the issue. ..." Regards, Ron Hello, RonSarid Please note that the size/space issue related to a failure to install KB2919355 has to do with the system reserved partition (often hidden in File Explorer), not the system volume (typically "C:" on Windows installs), as mentioned in the section about Error Code 0x800F0922 in the new Windows Help article " Install the latest Windows 8.1 Update ." More information about the system reserved partition is contained in the Windows Help article " What are system partitions and boot partitions? ", while a step-by-step guide on how to expand the partition is found in the Into Windows tutorial " How To Extend System Partition In Windows 8.1 ".

Thank goodness my dear mother is running Win 7. Much of this stuff will put even an advanced user in the weeds very quickly. It is truly amazing what people are willing to put themselves through in order to install this update, I can only imagine how all of this sounds to the typical user. After reading thread after thread it would appear a refresh or re-install would be much easier and less time consuming than some of the suggestions contained in these threads. But by all means, carry on and have fun trying to workaround, circumvent or find some way to install this obviously poorly designed and troubled update.

I am stuck with KB2961908 failing consistently with error 800F0922 and KB2919355 claiming it installed successfully but getting rolled back during the reboot. I downloaded the KB2919355 standalone installer, clearcompressionflag.exe ran without any output, running KB2919355.msu resulted in the same rollback. I noticed that during the restart the other 5 fixes in the KB2919355 package were installed but they were probably rolled back as well. sfc /scannow cleaned up a ton of errors relating to update files. A second sfc identified issues with the hash on CNBJ2530.DPB, a printer driver (could not be repaired). When I tried to install the standalone KB2919355 again, I received an error 80070003 (path not found). The WindowsUpdate.log shows "WARNING: Copy update to cache failed with exit code = 0x80070003". Windows Update Troubleshooter reports a DataStore 0x80070057 error that it could not fix and also "Access to the path 'C:\WINDOWS\softwaredistribution' is denied." I cannot see anything obviously wrong with this folder - permissions are identical to a similar system that successfully installed KB2919355 on May 4th. The WindowsUpdate.log contains numerous fatal errors including 0x800f0922, 0x8007045b, 0x80070002, 0x80242008, 80080008. Computer Management shows a 400MB Recovery Partition and a 300MB EFI System Partition. I pass HTTP traffic through a local squid3 server although this had not caused any issues in the past (most Windows Updates are too big to get cached). At this point, I am not sure if the next step should be the DISM tool, resetting the Windows Update components or restoring my system partition back to my last image backup on April 11 and hoping the problem goes away (:-). A step-by-step process for narrowing down the issues and appropriate remedial action would really help at this point.

partition size is 334 GB with 192GB free, so space is definitely NOT the issue. @ Ron The problem partition appeared to be the System partition. Supposedly something gets changed there. It is usually measured in MB. Use diskmgmt.msc to see them and how much Free Space there is. Use diskpart list volume to see more about it. However, I only know how to access it during a boot... OK. FWIW we can use diskpart to actually get to it, assign a letter to it and then do a dir! Who knew? And that shows that the last write was done 2014-03-02. Now what? Oh. I suppose I can use DISM /get-packages and try a find... Even better I can use Powershell's equivalent cmdlet and do the same thing... No. That doesn't make any sense. I only got this machine in April. ; / Ah. For my Surface RT 2 it may be a different story. With it when I delve into its System drive B:\EFI\Microsoft\Boot>dir/tw/od I see two relatively recent writes: 2014-02-22 07:17 760,680 bootmgfw.efi 2014-02-22 07:17 758,120 bootmgr.efi Then going into Powershell I get this: PS B:> Get-WindowsPackage -Online | ft InstallTime,PackageName -AutoSize | Out-String -Stream | Select-String -Pattern "2014-02-22" 2014-02-22 01:30:00 Package_for_KB291934~31bf3856ad364e35~arm~6.3.1.3 That was a transcription. I hope there aren't any typos but at least it will give you the right idea. There are some other directories that I didn't explore. Just trying to find something that would possibly match an update. But then it may only be a coincidence because the timestamps are not consistent with the update I found, so who knows? FWIW in my case it is a 200 MB partition with (according to dir) 178 free. But I also speculated to someone else making the same claim about their symptom that perhaps it could be referring to Virtual memory? Which I then tied to Marek's account about being rather meticulous about removing stuff that might have cost memory, e.g. if the programmer was trying to read everything in and use RAM. (My interpretation of what was done, not something that I read.) Or WinPE supposedly creates RAM drives, so maybe that was a "disk" that got too full. Again, who knows? For us, I think, only a trace can explain what is really going on. FYI Robert

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

2014-05-16T21:47:47+00:00

you would need to provide step by step instructions.

No. It is too speculative. It's just an idea for someone who does know what I mean and wants to try it. It's really more about exploring the scope of what we can do with DISM than anything positive that I know about or even have high hopes for. I may try this myself if I get a virtual machine set up to do it to.
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2014-05-16T22:22:24+00:00

"...My partition size is 334 GB with 192GB free, so space is definitely NOT the issue. ..."

Regards,

Ron

Hello, RonSarid

Please note that the size/space issue related to a failure to install KB2919355 has to do with the system reserved partition (often hidden in File Explorer), not the system volume (typically "C:" on Windows

installs), as mentioned in the section about Error Code 0x800F0922 in the new Windows Help article "Install the latest Windows 8.1 Update." More information about the system reserved partition is contained in the Windows Help article "What are system partitions and boot partitions?", while a step-by-step guide on how to expand the partition is found in the Into Windows tutorial "How To Extend System Partition In Windows 8.1".
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-16T22:35:06+00:00

Thank goodness my dear mother is running Win 7. Much of this stuff will put even an advanced user in the weeds very quickly. It is truly amazing what people are willing to put themselves through in order to install this update, I can only imagine how all of this sounds to the typical user. After reading thread after thread it would appear a refresh or re-install would be much easier and less time consuming than some of the suggestions contained in these threads. But by all means, carry on and have fun trying to workaround, circumvent or find some way to install this obviously poorly designed and troubled update.
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-16T23:10:59+00:00

I am stuck with KB2961908 failing consistently with error 800F0922 and KB2919355 claiming it installed successfully but getting rolled back during the reboot. I downloaded the KB2919355 standalone installer, clearcompressionflag.exe ran without any output, running KB2919355.msu resulted in the same rollback. I noticed that during the restart the other 5 fixes in the KB2919355 package were installed but they were probably rolled back as well.

sfc /scannow cleaned up a ton of errors relating to update files. A second sfc identified issues with the hash on CNBJ2530.DPB, a printer driver (could not be repaired). When I tried to install the standalone KB2919355 again, I received an error 80070003 (path not found). The WindowsUpdate.log shows "WARNING: Copy update to cache failed with exit code = 0x80070003".

Windows Update Troubleshooter reports a DataStore 0x80070057 error that it could not fix and also "Access to the path 'C:\WINDOWS\softwaredistribution' is denied." I cannot see anything obviously wrong with this folder - permissions are identical to a similar system that successfully installed KB2919355 on May 4th.

The WindowsUpdate.log contains numerous fatal errors including 0x800f0922, 0x8007045b,

0x80070002, 0x80242008, 80080008.

Computer Management shows a 400MB Recovery Partition and a 300MB EFI System Partition.

I pass HTTP traffic through a local squid3 server although this had not caused any issues in the past (most Windows Updates are too big to get cached).

At this point, I am not sure if the next step should be the DISM tool, resetting the Windows Update components or restoring my system partition back to my last image backup on April 11 and hoping the problem goes away (:-). A step-by-step process for narrowing down the issues and appropriate remedial action would really help at this point.
Was this answer helpful?

0 comments No comments
Anonymous

2014-05-16T23:34:57+00:00

partition size is 334 GB with 192GB free, so space is definitely NOT the issue.

@ Ron

The problem partition appeared to be the System partition. Supposedly something gets changed there. It is usually measured in MB.   Use diskmgmt.msc to see them and how much Free Space there is. Use diskpart list volume to see more about it. However, I only know how to access it during a boot...  OK. FWIW we can use diskpart to actually get to it, assign a letter to it and then do a dir! Who knew? And that shows that the last write was done 2014-03-02. Now what? Oh. I suppose I can use DISM /get-packages and try a find... Even better I can use Powershell's equivalent cmdlet and do the same thing... No. That doesn't make any sense. I only got this machine in April.   ; /

Ah. For my Surface RT 2 it may be a different story. With it when I delve into its System drive

B:\EFI\Microsoft\Boot>dir/tw/od

I see two relatively recent writes:

2014-02-22 07:17      760,680 bootmgfw.efi

2014-02-22 07:17      758,120 bootmgr.efi

Then going into Powershell I get this:

PS B:> Get-WindowsPackage -Online | ft InstallTime,PackageName -AutoSize | Out-String -Stream | Select-String -Pattern "2014-02-22"

2014-02-22 01:30:00 Package_for_KB291934~31bf3856ad364e35~arm~6.3.1.3

That was a transcription. I hope there aren't any typos but at least it will give you the right idea. There are some other directories that I didn't explore. Just trying to find something that would possibly match an update.   But then it may only be a coincidence because the timestamps are not consistent with the update I found, so who knows?

FWIW in my case it is a 200 MB partition with (according to dir) 178 free.

But I also speculated to someone else making the same claim about their symptom that perhaps it could be referring to Virtual memory?   Which I then tied to Marek's account about being rather meticulous about removing stuff that might have cost memory, e.g. if the programmer was trying to read everything in and use RAM. (My interpretation of what was done, not something that I read.) Or WinPE supposedly creates RAM drives, so maybe that was a "disk" that got too full. Again, who knows? For us, I think, only a trace can explain what is really going on.

FYI

Robert
Was this answer helpful?

0 comments No comments