Error 1935 with Office 2016 Standard Installation

Question

_{Friday, October 5, 2018 7:24 PM | 1 vote}

Hi everyone, hoping that someone has seen this before and has an idea as to why this is happening:

Brand new PC, protective labels are still on the face, just unboxed.  I've installed just a handful of our desktop software (Chrome, VLC, Teamviewer, etc).  This is a PC out of a batch of 5.  The other 4 did not have this issue.  Basically, Office will not install.  I've attempted to install the latest VLSC copy of 64 bit Office 2016 Standard, but it goes to about 75% and then fails.  There is nothing to uninstall afterwards as it "reverts" back.  I've tried my "old" copy, and also downloaded a fresh copy TODAY from the VLSC site, still no luck.

The error looks like this:

Any ideas are greatly appreciated & thanks.

All replies (29)

_{Monday, October 8, 2018 10:14 AM | 11 votes}

Hi,

You can try to install Office again by doing the following:

• Disable the three-party protection software, run the installer as an administrator, and install Office again.
• Use the Easy Fix Tool o15-ctrremove.diagcab to uninstall Office 2013 and install Office 2016 again.
• Use the .NET Framework Repair Tool .NET Framework Repair Tool to install Office again after the repair is complete.
• If you can't install Office using the methods above, you can try to run Windows in clean boot mode, only enable the system core service, and try to install Office again in this mode. Please refer to this document for specific methods: How to perform a clean boot in Windows

Note: Because you want to install Office in clean mode, you need to enable the "Windows Installer Service", the document also describes how to enable this service, you can refer to it.

If you have any question or update, please feel free to let me know.

Best Regards,

Herb Gu

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams

_{Thursday, October 11, 2018 1:45 AM}

Hi,

I am checking the status of this issue. Do you have any update for it?
If my reply is helpful to this question, please remember to mark it as answer. Your action would be helpful to other users who encounter the same issue and read this thread. Thanks for your understanding.

Best Regards,

Herb

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams

_{Monday, October 15, 2018 12:44 AM}

Hi,

This thread has been around for a long time. Please remember to mark the replies as answers if they helped. Please help us close the thread.
Thank you for understanding! If you have any question, or update, please feel free to let me know.

Best Regards,
Herb Gu

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams

_{Friday, November 2, 2018 1:19 AM}

Hi HPenk,

Any update here? Have you solved the problem? 

I'm looking forward to your response. If you have any additions, or update, please feel free to let me know.

Best Regards,
Herb Gu

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams

_{Tuesday, December 11, 2018 3:14 PM | 2 votes}

I don't know about the original poster, but Herb's solution worked for me.  I had already tried the removal tool, but couldn't get it to work until I ran the .Net repair tool!

Thanks,

Wendell

_{Tuesday, January 29, 2019 2:04 AM}

The  .NET Framework Repair Tool worked perfectly for me.

_{Thursday, January 31, 2019 2:23 PM | 3 votes}

I had the same 1935 error issue and it was driving me nuts as I'm an IT manager. Microsoft tech support was useless. I decided to reset the machine (Windows 10) as if it just came from out of the box from Dell. I set up a local account (didn't add the machine to the domain yet) and I also didn't connect to the internet in any way so that it didn't download any updates, etc. The first thing I did was to install Office (in my case, a VL version of Office Standard 2016) and (voila!!) it worked like a charm. I then proceeded complete the setup as I do with any other domain machine. I should also mention that, prior to doing it this way, I ran the .NET framework repair tool and that didn't work. I now know to do it this way for future setups. Good luck and hope this helps you.

_{Thursday, February 28, 2019 12:29 AM}

I ran the Easy fix tool and the .NET framework repair as Herb suggested.

Following a reboot, Office 2016 standard installed without issue.

 Thanks!

_{Tuesday, May 28, 2019 1:35 AM}

Thank-you Herb.

I bought a new Dell New XPS 13 Windows 10 Home laptop. First I face an activation error and then the error 1935 while installing Office 2016. I thought I may need to replace the laptop from Costco.

For the Windows Activation error - the 'troubleshoot' option fixed it - for the first time in my case.

For error 1935 while installing Office 2016, your option to download and run the .NET repair toolkit fixed the error.

You made my day and saved me a lot of heartache.

_{Saturday, June 22, 2019 6:29 AM}

Exellent Herb, Thanks a lot

This .NET Framework Rapair Tool Worked fantastic for me as well

_{Saturday, June 22, 2019 6:29 AM}

Herb's Suggestion worked for me very well

Thanks a lot

Exellent Herb, Thanks a lot

This .NET Framework Rapair Tool Worked fantastic for me as well

_{Friday, July 19, 2019 7:54 AM}

Let's sum up the facts here. 

1. This issue occurs with a Microsoft product. 

2. It occurs when installing the Microsoft product on a Microsoft OS even when no third party software is installed.

3. Microsoft isn't offering help.

It saddens me that in these days, people no longer gang up with pitch forks and torches to solve problems like this. 

_{Thursday, July 25, 2019 3:47 PM | 11 votes}

None of the options above worked for me. I have had this problem many times because I deploy all the new laptops for a large company. I am pretty sure this issue is caused by the version of office that is pre-installed from the Microsoft store.

I tried all the options suggested above. I tried manually removing the office Apps from the start menu by right clicking on each and choosing uninstall. I ran the office removal tool from the post above after this and it said no version of office was installed. I still got the 1935 error.

Delete this registry folder so office stops thinking it is an app and office installs fine. I hope this helps other people.

HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\APPMODEL

_{Friday, July 26, 2019 12:35 AM | 1 vote}

Tress,

I just encountered this problem with a brand new Dell OptiPlex I just tried to set up. As you suggested, deleting the AppModel regkey resolved the issue for me. Thanks so much!

Manny

_{Sunday, July 28, 2019 8:43 AM}

done thank you

_{Tuesday, August 13, 2019 5:09 PM}

the .net fix resolved my issue  -- thank you very much

_{Wednesday, August 14, 2019 2:20 AM}

This worked for me after trying everything else listed.

_{Tuesday, September 10, 2019 6:20 PM}

Thank you so much @Tress Schuyler for saving my day and time! Appreciate your tips.

_{Tuesday, September 17, 2019 8:34 AM}

Reg edit worked for me.

_{Tuesday, October 1, 2019 9:23 AM}

Solved my problem, thnx!

_{Friday, October 4, 2019 6:14 PM}

This worked perfect.  Just want to get this higher up on the fixes.  Brand new HP laptops fresh out of the box with this issue.  This has resolved it.

_{Wednesday, November 6, 2019 4:18 PM}

You can also remove Microsoft Office Desktop app under Apps and Features.  Removing it allowed me to install Office 2016.

_{Thursday, November 14, 2019 11:08 AM}

Using the .NET Framework Repair Tool fixed my issue.

Thanks Herb

_{Wednesday, November 20, 2019 10:12 AM}

thank you so much. my problem is resolve.

_{Monday, December 23, 2019 5:19 PM}

Tress Schuyler's registry trick worked for me!   The two repair tools had no impact on my problem.   Thank you Tress :)

_{Friday, February 14, 2020 1:44 PM}

This did the trick for me. Thanks very much for your help!

_{Friday, February 21, 2020 4:21 PM}

Go into regedit and rename the highlighted folder HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppModel

Install then works 

_{Thursday, March 12, 2020 12:19 PM}

Removing this key worked for me as well.

thanks

_{Saturday, March 21, 2020 5:34 PM}

worked perfect man