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

Was this answer helpful?

1300+ people found this answer helpful.
0 comments

141 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2019-04-17T13:03:43+00:00

    Just wanted to say thanks. I had a similar errorand I just wanted to post it here for others to find. Mine was:

    policy.14.0.microsoft.office.interop.access.dao

    This was office 2013 installed on a brand new HP Win 10 after Click to run was uninstalled.

    Thing is, that reg key has nothing in it apart from 1 subkey called Lookaside. Bad form Microsoft completely dying for such a trivial thing!

    I was thinking of ProcMon but wasn't relishing the filtering to find out what was cracking off, so once again, thanks for the answer, and thanks for saving me hours of Process Filtering!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-04-24T17:02:26+00:00

    Worked for me, thank you so much for this.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-04-26T20:51:06+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
    1. Registry key  - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppModel has multiple sub-registry keys 2) What did you exactly rename? Which word in this string of words ? Your explanation is not 100% clear.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2019-04-26T21:11:52+00:00

    631 people figured it out ;)

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppModel is the full registry path to a key.  The key is named "AppModel".  That's the key that needs to go (everything under it will "disappear" in the sense that MS will not find it, once you delete it or rename it).

    Try renaming AppModel to DumbAppModel.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments