Backward compatability?

Of course that was a Windows problem, and I meanwhile found ways to solve that. Perhaps the ccleaner is the suspect. I have to set the path at every session with the CommandPrompt.

Perhaps but maybe also a perspective view. For me it’s user’s problem. But by all means not a Windows problem since ALL OS’s behave equally in this regard.

Never. ccleanear does not touch the register other than to clean dead keys.

Oh dear, search the internet on how to permanently add something to the path.

Regarding ccleaner. That it cleans dead keys is the visible behavior for me, too; however, in the internet is described that it changes/changed the script for pathes. Hope it no longer does.

Regarding to set the path permanently: In several days I found no hint at all to that f… Ms cmdPompt, let alone this special item…

For thos who read my experience: Since today only the following works:

  1. Start ComandPrompt as Admin to get “C:\WINDOWS\system32>”
  2. Write path, in my case, “C:\programs\gmt6\bin\pscoast” (without “.exe”), which again ends with the above
  3. Copy or write script, e.g., “gmt pscoast … > C:\programs\GMT6\Test_B.ps”, which again ends with the above, now, however meaning that there is no Error and the tast is done. New experience yesterday: Any number in the output file can lead to misinterpreting it as input file!!
    Many thanks and best wihes to all
    Hans

It took me about ten seconds writing this in my browser’s search bar:

how to permanently make changes to windows path

Wow. The 14 steps with many caveats in wikihow? ok, but for me, one time a day copying the path into the cmdPrompt is sufficient.

Because my jobs are done, I wohld like to end the discussion here.
Thank You all for the hints.
Best, Hans