When I [Shift + Right-Click] a folder that isn't on my
C drive and select "Open console here" I get a
cmd window up that isn't opened at the correct location, but instead is pointing at
C:\Windows\system32. I have to manually switch to the correct drive, but when I do it is then at the correct folder. This is hardly the end of the world, but it's a minor annoyance that's really starting to get on my nerves...
Note: It does work correctly for locations on the
Is this the expected behaviour when used outside of
If not, how do I fix it?
If it is, how can I change it to load folders of other drives directly?
For example, if I attempt to open a console window pointing at a folder on my desktop, like so:
I get a
cmd window pointing at
C:\Windows\system32 that I have to manually switch to the
D:, but upon doing so you can see that the folder within
D: has been selected successfully:
It seems "Open console here" might be non-standard (see comments).
For completeness, it turns out that I see the probably standard "Open command window here" lower down the list when clicking inside a folder (it's "file space", not on the folder icon itself), as per the image below, so there's some difference between the two that's cropped up: