I think creating that registry entry is the responsibility of the application installer. You might try repairing the Office installation and see if that fixes it. Otherwise you can export it from a working machine and import it on the one without it, as long as Word is installed to the same path.

I see all the documentation from Microsoft, stating that this registry key should exist, but it appears that Microsoft has removed this registry key in the latest version of Windows 10. Every workstation I look at no longer includes this key. My personal workstation is certainly up to date and not a modified version of Windows, it does not include this key either. Microsoft must have removed it and did not update their documentation.

Opening a case with support, I am at loss here now that Microsoft has stopped using these registry keys with the latest version of Windows 10.

If the app can't find the path to the the office app, then we need to just manually provide the path, so that it can continue with it's operations.

That's more likely to be dependent on the version of Office you're installing, not Windows.

According to the article from Microsoft it was recommended that any app developers use this key, yet it no longer exists in Windows 10.

We recommend registering your application in the App Paths registry subkey. Doing so avoids the need for applications to modify the system PATH environment variable.

With one of our Windows 10 machines and Office 2016, it appears to use the location under HKEY_LOCAL_MACHINE. Your screenshot appears to have missed the "Microsoft" key.

Oh there is 2 Windows folders, I do see it now under Microsoft/Windows on my workstation. I will see if the user can check there again.

Hi Chad,

Did you ever get a resolution to this? We have a customer who moved to the new Licensing tier and now this issue started happening to random users when they try to use the Office Plugin via the Web Client. I doubt it is related to the license change and may just be a big coincidence but hoping you found a fix?

Thanks,

Ashleigh 

It got lost in the weeds, I think I heard that their IT department got something working, maybe by replacing the workstation. The app could really use a browse feature if it can't find word.exe automatically, where after choosing the executables location, it updates the proper registry values.