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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-01-18T04:49:27+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

    Brilliant! This made sense right from the start and worked quickly and easily. Thanks for the time you invested and shared!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2018-11-07T19:15:55+00:00

    Borro el AppModel o lo renombro?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2018-12-01T19:13:43+00:00

    Thank you friend, you are amazing. I am curious though, the process you used to track this down so that I could do this in the future.  Procmon? 

    Thank you again and if you find the time to reply, thanks.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2018-11-06T21:33:53+00:00

    THANK YOU...4 + hours of combing the net and all the forums looking for a solution...tried all the tools and suggestions,...nothing worked. Did exactly as you described here and it loaded no problem. Really appreciated your perseverance finding the answer to this one.

    Mike

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments