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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-05-31T11:46:37+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

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

    Commit 6:

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-05-30T18:20:13+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

    Thank you, thank you, thank you!!!  I tried everything for 2 days, but nothing worked until I discovered this cure.  Thanks a million!!!

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2019-05-28T10:46:29+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

    You are my savior!

    I got the same error when installing Office 2013 ProPlus.

    I noticed that the machine was previously installed Office from Microsoft Store, after uninstalled the Office on the Store, that Registry key was not removed, hence I have renamed the key as your mentioned and it works.

    Thank you a lot and have a nice day :)

    Was this answer helpful?

    0 comments