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
    2018-09-28T15:51:19+00:00

    Yes, or what I did is exported the key just in case i needed it and after the export just delete it.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-10-04T21:13:09+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

    Hi

    Got that error.  Follow many tips as

    • clean uninstall every office installed 
    • delete office folder in task scheduler
    • clean boot
    • sfc 

    and the only trick that solve the problem is by renaming that key

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppModel

    Thank you

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-10-09T19:15:09+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

    Just had this exact situation on a new Surface book we got in our district. Your fix worked! I was digging through the registry, but failed to notice the AppModel Key. Thank you for posting this.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments
  4. Anonymous
    2018-10-15T21:21:15+00:00

    Thanks a million. 

    Your solution worked for me!

    Was this answer helpful?

    0 comments