Share via

Office 2016 Professional Plus Error 1935 during installation

Anonymous
2018-08-11T05:48:30+00:00

I am getting the following error when I am trying to install Office 2016 on my brand new HP Pavilion laptop.

"1: 1935 2: BEA7209F-78B3-429E-B4DO-E647E16A2604) 3: 0x80131049 4: IAssemblyCacheltem 5:

Commit 6:

Policy.12.0.Microsoft.Vbe.lnterop,fileVersion "15.0.4420.1017",version-"15.0.0.0000000",culture

Setup failed. Rolling back changes..."

Please help

Microsoft 365 and Office | Install, redeem, activate | For home | Windows

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

Answer accepted by question author

  1. Anonymous
    2018-08-28T18:51:14+00:00

    I pulled my hair out for about 12 hours before I resorted to using procmon to see what the heck was causing the issue.  I tracked it down to a registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppModel

    Right before the install fails, it checks this key, which my other machine didn't have at all.  It seems to be something related to apps installed through the store (this had 365 which was uninstalled previously).  I simply renamed the key and the install worked fine.

    Things that didn't work:

    1. sfc /scannow
    2. DISM repair
    3. .net repair tool (didn't really do much and found no errors)
    4. Office removal tool (said it wasn't installed)
    5. Rebooting
    6. cleaning temp folders

    1300+ people found this answer helpful.
    0 comments

141 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-08-16T02:08:53+00:00

    Just fixed Mine. try the .NET framework repair tool. I guess uninstalling the free junk messed with something and the tool fixed it right up. Give it a shot. I'm anxious to know if it helps you.

    80+ people found this answer helpful.
    0 comments
  2. Anonymous
    2018-08-23T08:05:02+00:00

    I received the same 80131049 error when installing Office 2013 on a new laptop running Windows 10 1803.  Prior to build 1803 I had not encountered a problem.

    The .NET Framework Repair Tool fixed the problem for me, downloaded from

    https://www.microsoft.com/en-us/download/details.aspx?id=30135

    40+ people found this answer helpful.
    0 comments
  3. Anonymous
    2018-08-29T16:19:12+00:00

    I pulled my hair out for about 12 hours before I resorted to using procmon to see what the heck was causing the issue.  I tracked it down to a registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppModel

    Right before the install fails, it checks this key, which my other machine didn't have at all.  It seems to be something related to apps installed through the store (this had 365 which was uninstalled previously).  I simply renamed the key and the install worked fine.

    Things that didn't work:

    1. sfc /scannow
    2. DISM repair
    3. .net repair tool (didn't really do much and found no errors)
    4. Office removal tool (said it wasn't installed)
    5. Rebooting
    6. cleaning temp folders

    This worked like a charm. Thank you so much.

    20+ people found this answer helpful.
    0 comments
  4. Anonymous
    2018-08-31T08:17:01+00:00

    I pulled my hair out for about 12 hours before I resorted to using procmon to see what the heck was causing the issue.  I tracked it down to a registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppModel

    Right before the install fails, it checks this key, which my other machine didn't have at all.  It seems to be something related to apps installed through the store (this had 365 which was uninstalled previously).  I simply renamed the key and the install worked fine.

    Things that didn't work:

    1. sfc /scannow
    2. DISM repair
    3. .net repair tool (didn't really do much and found no errors)
    4. Office removal tool (said it wasn't installed)
    5. Rebooting
    6. cleaning temp folders

    I don't have that much hair but it costed me also a few hours to find your post.

    After deleting that key MS office installed fine.

    Thx

    10+ people found this answer helpful.
    0 comments