Error: 0x800F0922 when installing KB 2919355

Anonymous
2014-05-14T19:23:49+00:00

This error may appear for multiple reasons. Some common causes are VPN clients and an unexpected System Reserved Partition size.

Try removing any VPN Clients and attempt the update again.

You might be able to fix this problem by using third-party software to increase the size of the System Reserved partition.

If you have tried both solutions and you still experience Error 0x800F0922 please contact Microsoft Support so that we can further investigate your issue.

Windows for home | Previous Windows versions | Windows update

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 No comments

178 answers

Sort by: Most helpful
  1. Anonymous
    2015-04-20T01:09:17+00:00

    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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2014-06-10T21:28:55+00:00

    Hi guys,

    I was also struggling with these issues for many weeks now, and finally got it working today:

    I just cleaned up my machine a little bit by removing SonicWALL VPN Client, OpenVPN, another VPN manager and a partitioning tool. I guess it had something to do with VPN indeed.

    I made sure that no VPN adapters/connections remain (only standad ethernet adapter).

    After that, I normally installed update 2919355 using Windows Update. During downloading I additionally disabled Windows Defender, since it seemed to be quite active by checking the update (according to Task manager) - I just wanted to go sure that it doesnt affect the installation process.

    Thats all - really helped me out.

    Best Regards and good luck,

    Andreas

    PS: It's still a shame that such things can break a system update installation.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2014-05-16T20:55:12+00:00

    I was not overly concerned about the issue with KB2919355, figuring I would sort it out eventually, until KB2961908 also failed.  I’m cross posting this under both the 80073712 & 8000f0922 threads as I’ve seen both errors.

    I was able to do a full image restore dating back to Dec 22, 2013 after a clean boot.  After the full image restore I reran DISM … /restorehealth and came up with the same …providers.dll’s failing to load as before the rollback.  They are PEprovider, WOW64provider, Embeddedprovider.   

    My thinking is to correct these 3 issues and slowly walk the system back to the point of attempting KB2919355.   Below are the excerpts from the log surrounding the failures.  Let me know if you want the full log and/or the Cbs persist --- .cab files

    I was not overly concerned about the issue with KB2919355, figuring I would sort it out eventually, until KB2961908 also failed.  I’m cross posting this under both the 80073712 & 8000f0922 threads as I’ve seen both errors.

    I was able to do a full image restore dating back to Dec 22, 2013 after a clean boot.  After the full image restore I reran DISM … /restorehealth and came up with the same …providers.dll’s failing to load as before the rollback.  They are PEprovider, WOW64provider, Embeddedprovider.   

    My thinking is to correct these 3 issues and slowly walk the system back to the point of attempting KB2919355.   Below are the excerpts from the log surrounding the failures.  Let me know if you want the full log and/or the Cbs persist --- .cab files

    JUST HAD THE OPPORTUNITY TO RUN DISM ON A SIMILAR PC - SAME ERRORS SHOW UP - HOWEVER KB2919355 IS SUCESSFULLY INSTALLED.   -  LOOKS LIKE THIS EXERCISE WAS A WASTE OF TIME.

    2014-05-11 15:41:32, Info                 <br>DISM   DISM Provider Store: PID=5896 TID=5320   Provider has not previously been encountered.   <br>Attempting to initialize the provider. -   CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:32, Info                 <br>DISM   DISM Provider Store: PID=5896 TID=5320   Loading Provider from location   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\PEProvider.dll   - CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:32, Warning              <br>DISM   DISM Provider Store: PID=5896 TID=5320 Failed   to Load the provider:   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\PEProvider.dll.   - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2014-05-11 15:41:33, Info                 <br>DISM   DISM Provider Store: PID=5896 TID=5320   Provider has not previously been encountered.   <br>Attempting to initialize the provider. -   CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:33, Info          <br>       DISM     DISM Provider Store: PID=5896 TID=5320 Loading Provider from location   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\Wow64provider.dll   - CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:33, Warning       <br>       DISM     DISM Provider Store: PID=5896 TID=5320 Failed to get the IDismObject   Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
    2014-05-11 15:41:33, Warning              <br>DISM   DISM Provider Store: PID=5896 TID=5320   Failed to Load the provider:   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\Wow64provider.dll.   - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
    2014-05-11 15:41:33, Info                 <br>DISM   DISM Provider Store: PID=5896 TID=5320   Provider has not previously been encountered.   <br>Attempting to initialize the provider. -   CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:33, Info                 <br>DISM   DISM Provider Store: PID=5896 TID=5320   Loading Provider from location   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\EmbeddedProvider.dll   - CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:33, Warning              <br>DISM   DISM Provider Store: PID=5896 TID=5320   Failed to Load the provider:   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\EmbeddedProvider.dll.   - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2014-05-11 15:41:32, Info                  <br>DISM   DISM Provider Store: PID=5896 TID=5320   Provider has not previously been encountered.   <br>Attempting to initialize the provider. -   CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:32, Info                  <br>DISM   DISM Provider Store: PID=5896 TID=5320   Loading Provider from location   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\PEProvider.dll   - CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:32, Warning               <br>DISM   DISM Provider Store: PID=5896 TID=5320 Failed   to Load the provider:   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\PEProvider.dll.   - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2014-05-11 15:41:33, Info                  <br>DISM   DISM Provider Store: PID=5896 TID=5320   Provider has not previously been encountered.   <br>Attempting to initialize the provider. -   CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:33, Info                  DISM    <br>DISM Provider Store: PID=5896 TID=5320 Loading Provider from location   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\Wow64provider.dll   - CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:33, Warning               DISM    <br>DISM Provider Store: PID=5896 TID=5320 Failed to get the IDismObject   Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
    2014-05-11 15:41:33, Warning               <br>DISM   DISM Provider Store: PID=5896 TID=5320   Failed to Load the provider:   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\Wow64provider.dll.   - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
    2014-05-11 15:41:33, Info                  <br>DISM   DISM Provider Store: PID=5896 TID=5320   Provider has not previously been encountered.   <br>Attempting to initialize the provider. -   CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:33, Info                  <br>DISM   DISM Provider Store: PID=5896 TID=5320   Loading Provider from location   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\EmbeddedProvider.dll   - CDISMProviderStore::Internal_GetProvider
    2014-05-11 15:41:33, Warning               <br>DISM   DISM Provider Store: PID=5896 TID=5320   Failed to Load the provider:   C:\Users\ABCDE_~1\AppData\Local\Temp\2DF12B6C-680B-49A3-AE7A-035CE8AD29A7\EmbeddedProvider.dll.   - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-05-16T19:11:12+00:00

    You should not. It should be a free call.

    Shoulda woulda coulda.

    ¯\_(⊙︿⊙)_/¯ Microsoft.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-05-16T19:07:41+00:00

    Removing and reinstalling my VPN client or adjusting the partition size may work fine on a single workstation, but it will definitely not work across the board in a large environment.

    Was this answer helpful?

    0 comments No comments