Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
I totally get it. I just wanted to make sure you had tried it. You probably had to scroll pretty far down to see that possible solution.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I keep getting error 1935 when trying to install Office Standard 2016 on a brand new PC running Windows 10 for workstations build 1803. I have tried:
Here's the build process:
Gotten this error on 4 consecutive machines.
Tried items suggested here:
but to no avail.
Any ideas?
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
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.
I totally get it. I just wanted to make sure you had tried it. You probably had to scroll pretty far down to see that possible solution.
Sorry, forgot to mention that the registry keys didn't work for me last time. Haven't tried them this time.
If you set up multiple laptops every week its probably the same every time.. i see this issue 4-5 times a year on different machines and what helps one time doesn't the next time.
Did you ever try the registry change by ToddStarlin? This has been fixing it on every new laptop I purchase for my company. It is a lot faster than reinstalling Windows. By clean install, do you mean a different version of Windows from CD or a Flash drive? If you mean factory reset, I could see the problem still occurring. As soon as Windows opens for the first time, the App store starts trying to do a bunch of updates on all the Apps including the pre-installed App version of Microsoft Office that comes with Windows 10. If you go in the store and find your way to updates you will see them all downloading like crazy without asking you.
The registry fix removes the folder that causes Office to think it is a Microsoft Store App and not a standalone version that is installed. Removing the folder from the registry has been fixing this issue for many users on different forums. This is faster and possibly less dangerous than messing with changing .net when it probably didn't need it. This is of course my opinion, but I set up laptops multiple times a week and this has been a ridiculous problem until I found the registry fix.
I have only ever had to remove this one folder and it always works. H****KLM\Software\Microsoft\AppModel
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
.NET Repair tool fixed this for me today. Last time it didn't, then I did a clean windows install, uninstalled the office bloatware, NO updates and then I could install office before the windows updates. This time office would not install before the updates so I'm guessing this machine came with a newer Windows 10 than the last one I set up a few weeks ago.