Closed sql-sith closed 6 years ago
I was able to find some references to the old installation in c:\util\cmder
in the registry. After verifying that they were unnecessary since they were pointing at this directory that no longer exists, I deleted those entries, and all of my tasks function correctly now. Maybe this will help somebody else who has the same issue at some point.
Purpose of the issue
Description of the issue
Hi! I am just getting used to Cmder+ConEmu, and am liking it. Thanks for your hard work!
I have a laptop on which I
c:\util\conemu
c:\util\cmder
(maybe I removed conemu first? I don't remember)c:\tools\cmder
Well, that's mostly accurate. :)
The deal is, I think that when I "removed all of that" that I may have missed some items. My immediate problem is that my Powershell admin task has a value for
Env:\CMDER_ROOT
that points at a location inc:\util\cmder
. This is not a big deal, but it keeps my Powershell profile from loading. I could fix that by editing theuser-profile.ps1
that is insidec:\util\cmder
but I'm concerned that I might be missing some other detritus from my previous installations.The
Env:\CMDER_ROOT
variable is set correctly toc:\tools\cmder
when I run a Powershell non-admin task.All of that to ask this: I want to go over every source from which the
Env:\CMDER_ROOT
variable could be set. Can you give me that information?I am using Windows 10 with the April 2018 update and Cmder 180206.
Cheers, Chris