Forum Discussion
Error message: “the operating system is not configured for that operation”
Can you give a bit more detail on what you are doing to the machine before this error occurs?
For example, the machine has a previous version of Office 2013 C2R, or Office 2013 MSI (Volume License) and you are trying to upgrade to Office 2016 C2R using [Manual Install/Group Policy/Script/Configuration Manager/Other] ?
I have not encountered this error before so it makes me think it has to do with the steps that are being performed on the machine to cause this to happen.
Also, just curious, does going into Control Panel and doing an "Online Repair" fix the problem (as a work-around?).
Is this problem happening on all 150 systems now or just the ones you are upgrading?
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.
- Joe StockerNov 01, 2017Bronze Contributor
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.
- Shane BryanNov 01, 2017Iron Contributor
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.
- Shane BryanNov 11, 2017Iron Contributor
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.