Error: 0x800F0922 when installing KB 2919355

Demand a refund you should not be charged for this issue

I had this problem at home and you guys had to download an ISO to reinstall 8.1.

I had the same error code at church and the tech spun her wheels all day.  After I paid $149 for support, all she could do is repeat the same install five times and fail five times.  Her parting shot was that she would have to bump it up to a higher level and they are supposed to call me tomorrow.

I bought this software in December and the patch failed in April.  Now I have paid an additional $149 to fix a problem that Microsoft caused. (case #1250789517)

I call it highway robbery.

After all the head scratching, I finally caved in and called MS support and spent a little over 2 hours on the phone.  It would have been longer but the call ran into the centers quitting time.  Essentially support repeated a few of the steps I took but with a couple of variations.  The significant new steps were –

Ran DISM /online /cleanup-image /startcomponentcleanup

Rebooted

Verified KB2919442 was installed (it was)

Downloaded the individual components of KB2919355 from

http://www.microsoft.com/en-us/download/details.aspx?id=42335

Closing time came right as KB2919355 was running and I was instructed to follow the order below -

Clearcompressionflag.exe, KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018.  This took the better part of 2 hours albeit I wasn’t glued to the desk all the time.  A Level 2 call was set up for this morning which turned out to be unnecessary because after installing all of the components w/o any errors the OS seems to be running fine. 

On a side note, I would recommend installing EMET 4.1 for additional protection.

I've been dealing with trying to update my 4 month old ASUS laptop (that came with Windows 8.1) since this update came out with ZERO success.

Okay, I ran DISM /online /cleanup-image /startcomponentcleanup which completed successfully. I downloaded the individual components of KB2919355 successfully (no errors). I ran Clearcompressionflag.exe with no errors reported. I tried to install the KB2919355 component. The install went fine, the installer said successful install, need to reboot. It rebooted and proceeded to continue the update. It seemed to be going well, but when I looked back, the screen said "We couldn't complete the updates, undoing changes..."

Bottom line, this procedure did not work for me.

Okay Microsoft, I've been using MS Windows since version 3.1. I have installed, uninstalled, reinstalled, recovered, updated rewinded updates, restored and done just about anything that can been done to Windows. I build & repair computers for a living and install Windows, Linux, OSX, BSD, Lynx, VxWorks, QNX to name a few. This update is an unmitigated disaster. I have *never*, and I repeat *never* had this much problem trying to update a supposed commercial operating system. The incompetent managers and software engineers who released this, made this a mandatory update and shoved it down our throats should be fired and not allowed near a computer for 5 years. This is a major fail for Microsoft. Even their support techs don't know how to approach this.

Hi,

I had exactly the same problem here with error code 800F0922. This was on a Dell XPS 12 running Windows 8.1 Pro x64.

I tried many of the suggestions listed here and elsewhere, including using the SFC and DISM tools but nothing worked.

However, once article I read mentioned the possibility of VPN software stopping it from installing. We use the Check Point Endpoint Security suite and a component of this is a VPN solution. I removed this but it made no difference. Then I decided to remove the entire suite, which also includes Full Disk Encryption, a Firewall and Media Encryption, for USB devices.

After this was removed and the disk was completely decrypted I attempted the install again, using the downloaded MSU file, file size 724,339,463 bytes.

This time it worked! I don't know what was stopping it but my guess would be something to do with the FDE component, as it does encrypt all partitions. Maybe there is some truth behind the idea that it could be free space on the System Reserved partition but I don't know for sure.

Anyway, hope this helps someone out there!

Howard

Hi. I have a question about this (and the other) proposed solutions -- how does KB2961908 ("security update for x64-based systems without KB2919355 installed") tie into these solutions? I'm getting error 800F0922 when trying to install KB2961908 -- my impression was that it is best to get this one installed first before trying to get KB2919355 working.. not sure if that is actually the case?

I can't recall at this point if I've already tried (and failed) to get KB2919355 itself installed after the former failed, and I'm bit reluctant to try to do so until figuring out what is the expected order.

Oops, looks like I've finally found a resolution for the KB2961908 installation issue independently of the above (for other folks faced with both, it was to first disable Secure Boot in the UEFI firmware).  Please disregard the question.

So now I'm left with KB2919355.. and after reading some of the above, I'm nervous about trying to install it via Windows Update vs downloading and installing standalone. I gather the latter might be safer.

Actually, I just checked my update history and confirmed that indeed, I'd been disciplined and hadn't yet tried to install KB2919355 at all before sorting out the KB2961908 issue.  Given all of the discussion above, how serious is the likelihood of attempting KB2919355 from Windows Update causing some form of filestore corruption? Is it indeed the general recommendation at this point for folks who haven't attempted it yet to prefer a standalone installation to Windows Update?