Forum Discussion
Error message: “the operating system is not configured for that operation”
This is happening on devices that have brand new installs of the Office 2016 C2R from the office portal, done manually.
Doing an online repair doesn't fix the issue either.
It seems to be happening on systems that are the most up to date with Office updates.
Was there ever any previous version of MS Office on the machine? It sounds to me as if there is a lingering component from a previous install that was not uninstalled.
Prior to installing O365 C2R, all previous versions of C2R or MSI including Project and Visio and shared components need to be scrubbed from the machine.
There are a few automated scripts available in the community that can help scorch previous office installs.
Or is this a brand new machine that you are experiencing this behavior with? There has to be something on the machine causing this, otherwise all of us would be seeing what you are experiencing.
My device may have traces of older Office versions, but I know that my managers one does not. When he started we imaged it fresh, to put the 1709 update onto it. Now, 1 week later he's getting the same error I do.
I've since discovered that my managers device only had W10 build 1703.
I have updated mine to 1709 and the problem has gone away. We will update a few others experiencing this issue and see if it resolves this for them also.
Did you ever resolve this problem? We're also seeing it on a number of machines, but not all. We image all of our systems and then add additional apps as needed with SCCM. I'm suspecting it's one of those additional apps which is causing the problem.
- Since the problem did not immediately appear on the manager's workstation, I would look in the event log around the time he/she first saw the error, perhaps something is getting installed on the machine that is causing this behavior to occur. That would make sense because a freshly imaged machine may not have all the apps the manager needs, then a week later they install an app and WHAM.. it causes this problem. My recommendation is to start again with a fresh image, then see if the problem occurs, watching the event logs for evidence of what is getting installed on the device.
