Error: 0x800F0922 when installing KB 2919355

After a lot of research, everything failed before, manual install, removing symantec, DSIM tools, making more space to drive C. etc.

This one worked for me!!

Remove this registry keys

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers{e7ef96be-969f-414f-97d7-3ddb7b558ccc}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers{8c416c79-d49b-4f01-a467-e56d3aa8234c}

I got this info from Here, hopefully works for somebody else

https://social.technet.microsoft.com/Forums/windows/en-US/70219bcb-36a8-466e-900b-cbf390db38d2/failure-configuring-windows-updates-reverting-changes-postreboot-status-0x800f0922?forum=winserver8gen

If you don't use bitlocker, simply delete the System Reserved partition, as it's not needed.

You will have to do a few things prior to doing so:

1. Move boot files from the system reserved partition to the system partition
   1. Open admin command prompt:
      • *bcdboot C:\Windows /s C:*
      • diskpart
      • lis vol
      • select vol<System Volume>
      • act
      • lis vol
      • sel vol<System Reserved Volume>
      • inactive
      • exit
   2. Configure BCD:
      • bcdedit /set {bootmgr} device partition=C:
      • bcdedit /set {default} device partition=C:
      • bcdedit /set {default} osdevice partition=C:
   3. Before rebooting, please make sure you have either a Windows installation DVD or WinPE/WinRE cd/usb flash drive to boot from if Windows fails to boot. If Windows doesn't boot, boot from install disk or WinPE/WinRE and at the command prompt type:
      • bootrec /fixmbr
      • bootrec /fixboot
      • bootrec /rebuildbcd

Once rebooted, move WinRE from the system reserved partition to the system partition

1. Open admin command prompt
2. Assign a drive letter to the recovery partition in diskpart:
   • diskpart
   • lis vol
   • sel vol<Recovery Volume>
   • assign let=R
3. Disable WinRE**:**
   • reagentc /disable
4. Remove WinRE from Reserved partition:
   • rd R:\Recovery
5. Copy WinRE to System partition:
   • robocopy C:\Windows\System32\Recovery\ R:\Recovery\WindowsRE\ WinRE.wim /copyall /dcopy:t
6. Configure WinRE:
   • reagentc /setreimage /path C:\Recovery\WindowsRE
7. Enable WinRE:
   • reagentc /enable

Depending on your available space on your hard drive, you may find it useful to create a new partition at the end of the drive (after the OS partition) and store WinRE and, depending on size, an OSI folder (Original System Installation) which contains all files contained within the Windows 8.1 ISO or DVD.  If you choose to, it's important when you create the Recovery partition that you set the partition ID flag to 27 (0x27) using diskpart, as that designates it as a Recovery Partition.

For example. I have a 250GB recovery partition that houses WinRE, OSI, and a recovery wim of my system with all desktop applications installed.  I've also edited the BCD to display the the 3 boot options (Windows 8.1, WinRE, Win 8.1 OSI) prior to booting Windows, as this allows a recovery of the OS if for some reason WinRE won't boot.

how much should be the System Reserved Partition. Mine is 500 mb. do you think its insufficient?

I do not use VPN.

please help.

this issue is since I purchased the system which is Dell  Inspiron laptop.

TIA

I understand the frustration, but if you re-analyze a few things you stated, you may see how irrational they are and (at least to me) seem to be said out of frustration:

"I am simply stating the lack of choice MICROSOFT has offered me"

They've offered two choices: research and try to troubleshoot yourself, or a remote tech session.  A remote tech session solves two issues for the end user, 1: it's convenient, 2: it saves them the time of searching and troubleshooting on their own.  There's a lot with Microsoft to take issue with, free remote tech support is not one of them.  Many software companies charge for that type of support, and it's more secure than taking your computer into someplace to have "repaired" (almost 99% of which have very little understanding of Microsoft Windows, and utilize a one click dvd to check for issues). With remote tech support, you literally control every part of the remote experience and can terminate immediately if you feel they're being too intrusive.  The remote session isn't sending files to you, it's a remote desktop experience that simply allows them view your screen on their computer to have a gui to work with... nothing more. 

"I am told the only way to fix it is to let them remotely access my computer"

Above applies to this as well 

"As far as "SOMEONE" screwing up my system partition, that was set by the install and "They" being me, had nothing to do with that."

Then that's not your problem... if you review the reason why the system partition becomes an issue, it's not because it was set up and left alone.  Again, unless you utilize bitlocker, move your boot files to the C drive via command line and delete that partition.  The system partition should ONLY be created if you intend to use bitlocker, and if you don't, manually remove it prior to install in the future.  WinRE, however, SHOULD be on a separate partition, and while it does occasionally get placed on the system reserved partition, WinRE operates best when you customize it and afterwards should be on a partition larger than 350MB.  In my opinion, it's best to keep WinRE, an OSI folder (Original System Installation, i.e. a copy of the OS's install files from the iso or DVD), and a custom recovery wim image on a Recovery Partition .  My recovery partition which houses all of those is ~ 230GB (~ 210GB is the wim recovery image).  (If creating a custom recovery WIM, do not utilize the refresh feature, and simply format and restore the wim recovery image directly to the system partition, Refresh causes Windows to be re-activated and if you change the computer name, you will run into activation issues, on top of the fact most software will also require reactivation. While a "refresh" feature is important in smartphones and tablets, scale the size of the HDD and complexity of the OS above that of a smartphone/tablet, and the "refresh" option becomes inefficient and problematic.)

"That being said I think I will exercise my freedom and revert back to windows 7 where I had ZERO problems"

This isn't an actual solution and in the large scheme of things, creates more problems than it solves. It is because Microsoft has to support obsolete OS's that issues with current OS's aren't given full attention. Consider the billions of devices running a version of Windows and consider most of them don't run Windows 8.1.... That takes serious amounts of resources out of Windows 8.1 troubleshooting within Microsoft.  Consumers that choose to downgrade ensure that problems like this will continue to occur within both current, and future, OS's.  On top of that, the reason for the error you're experiencing, is user customization, not the OS itself.  You can't seriously expect Microsoft to customize updates and tailor them to each and every one of the billions of devices running Windows.

"I think Microsoft would take more time to listen to customers and not try to pressure them by making the only solution something that makes them uncomfortable"

They have with Windows 10, and not only listen, but respond directly to users as well with concerns or suggestions... they've learned from trying to be too ahead of the curve, which is what Windows 8 was.

Again, there are multiple solutions to your problem, and comes down to whether you want to troubleshoot yourself or have remote tech support... they've given you all the tools and it's not their fault if an end user refuses to utilize those tools and help themselves.

Not to mention think about it.  We want Microsoft to have support staff get all the log files in order to make sure this fiasco never happens again.  It's only when they remote in can they review a system to know what's going on.