Error: 0x800F0922 when installing KB 2919355

Anyone with a computer problem has 1 of 2 choices... Either take the time to research the problem you're having and fix it yourself, or allow someone else to, either via physically taking the computer to a repair center or by having someone remotely connect to the device.

If you aren't willing to allow tech support to remotely connect, when you have complete control over the connection the entire time, are able to view everything they do, and can disconnect immediately at any point, then take the time to research why you're having the issue and how to fix it.

What you shouldn't do is complain about refusing to help yourself...

EDIT:

Be aware, you're having this issue because you either made a customization to the OS that is interfering with the update, i.e. a VPN connection, or you, or whomever you had install the OS, screwed with the reserve partition the Windows Installer auto sets, and is only changed by user interaction.  

If the reserved partition is the issue, and you do not use bitlocker, simply get rid of it, as it's not needed and causes more problems than it's worth (which prevent windows from booting when issues do arise, as it's where the boot files are stored).  It's simple to move the boot files to the system [C:] partition and guides can be found on numerous forums

OK, I am not complaining any anyway, I am simply stating the lack of choice MICROSOFT has offered me. It is more than obvious that NUMEROUS people have had this issue and I am told the only way to fix it is to let them remotely access my computer. I mean what is that. If you have the fix as the woman claimed, then put it out, or don't lie to me and say you do and you are going to "TRY" something. 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. If it IS the size of the partition, why hasn't Microsoft sent out a optional update or patch for that? I have been a LOYALY Microsoft customer since Windows 98 and I am just totally disappointed in the newer software. That being said I think I will exercise my freedom and revert back to windows 7 where I had ZERO problems. But that is personal preference. I will look into the VPN suggestion and also the EaseUS partition suggestion. But for all the comments I have seen regarding recent update issues, 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. That's my opinion.

* EDIT: OK maybe I was complaining a little there.

There are some support tasks that just can't have an automatic fix.  You also have to keep in mind the translation problem.  The people that Microsoft hires are not native English speakers (typically) so what they said "we have a fix" is not what they mean.  They probably truly do mean "I will try to fix your machine" not "we have this super duper automatic this will fix ANYTHING and we can send the hotfix to you and you can fix it yourself".

Support does remote into systems all the time.  It's the most efficient way to fix things.  Otherwise you'd have a lot of back and forthing and there's possibilities that you may not understand the instructions.  Especially for lingering KB2919355 issues, this isn't something that one can fix WITHOUT remote access to a machine.

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.

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.