Hey @SherifTarabishy, I installed 19043.928 on a VM and couldn’t reproduce this. I’ll get back you shortly with some tests that we can run to figure out what’s wrong.
I am also facing the same error. I was running Rhino 7.19 earlier without any issue. Today I updated to 7.20 and got this message when I started Rhino.
I uninstalled and re-installed but still facing the same issue.
Can you please download and run the diagnostic tool below and let me know what it returns? I think that something is causing Rhino to incorrectly detect that it’s running in a containerised environment (i.e. docker). This tool runs through the same checks that Rhino does on startup and returns an identifier for the check that is causing the false positive.
Very odd. The CExecSvc service should only run inside a Windows container. I’ve read about cases last year when Microsoft accidentally pushed out updates intended for containers to regular desktop systems. Try stopping the service (Start > Services then right-click on the CExecSvc service and choose Stop) and run the diagnostic tool again. Let me know if it prints “OK”, or not!
But, Windows container is also runnable on Windows Pro & Enterprise, which might not be a good server indicator (and some software may use it? maybe Isolation Mode of Edge, Android virtualizer like BlueStacks, etc).
The CExecSvc service should only be running inside a container, not outside. Here’s a thread that describes something similar, albeit on Windows Server.
You can try deleting the CExecSvc service and also look for a file named C:\License.txt and delete/rename it if it exists.
Things have moved on in the Windows container world and we may no longer need to perform the same checks to detect when Rhino is running in one. I’ll see if we can fix this on our end…
Out of four CExecSvc. exe files found on my system, I was able to successfully able to rename two files by changing their ownership by running the ‘TAKEOWN /F’ command in the admin command prompt and also in the properties>security>advanced section.
I used the same process for changing the ownership of all these files but for the two files, I am getting this error when I try to rename or delete them.