No REG Command in "Open elevated command window here" DOS Box

MilesAhead said:

Brink said:

It wouldn't be the "explorer.exe" process. It should be a "cmd.exe" process instead of a "cmd.exe *32" one.

Did you merge the Default_CMD.reg instead earlier?

If you like as a test, create a new administrator account to see how it works while logged on to the new account.

It would be Explorer.exe if he ran it by double clicking the .reg file in a 32 bit instance of explorer. Whichever it is, it still sounds like he's getting the 32 bit emulation redirection.

I have my own PromptHere you can download here:
http://www.favessoft.com/hotkeys.html

It has the ahk source code. You can download AHK_L and compile in 64 bit if you want. Anyway, it doesn't rely on the registry since it doesn't do context menu. It uses a hotkey. Select a folder and hit the hotkey.

Uses optional blur window on W7.

Sorry, I was thinking of the process for the command prompt for "Open elevated command window here".

fwcetus said:

Update: (and, before having a chance to mull over MilesAhead's post)

I happened to try "Open[ing] Command Window Here as Administrator", with "C:\Windows\System32\" as the directory, and then with "C:\Windows\SysWOW64\" as the directory, and, in both cases, REG works as it should.

However, selecting any other directory (including other ""C:\Windows\" subdirectories) and "Open[ing] Command Window Here as Administrator" results in a CMD box where REG does not work.

Reg.exe is, of course, located in both "C:\Windows\System32\" and "C:\Windows\SysWOW64\", not surprisingly.

Strange...

echo %path%
please post output

Brink said:

It wouldn't be the "explorer.exe" process. It should be a "cmd.exe" process instead of a "cmd.exe *32" one.

Did you merge the Default_CMD.reg instead earlier?

If you like as a test, create a new administrator account to see how it works while logged on to the new account.

OK. Every explorer.exe is a 64-bit process.

When I use the CMD box from Accessories, it runs as a 64-bit process.

However, any CMD box that comes up from the context menu, whether it's the "regular" CMD window from the "Open command window here" menu item, or the CMD window in question here from "Open elevated command window here", is running as a 32-bit process.

Yes, I did use the Default_CMD.reg file.

echo %path%
C:\BatCom\;C:\Programs\SscePortable;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windo ws\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\C ommon Files\Lenovo;C:\Program Files (x86)\Common Files\Ulead Systems\MPEG;C:\Program Files x86)\Windows Live\Shared;C:\SWTOOLS\ReadyApps;C:\Program Files (x86)\ Intel\Services\IPT\;

Brink said:

MilesAhead said:

Brink said:

It wouldn't be the "explorer.exe" process. It should be a "cmd.exe" process instead of a "cmd.exe *32" one.

Did you merge the Default_CMD.reg instead earlier?

If you like as a test, create a new administrator account to see how it works while logged on to the new account.

It would be Explorer.exe if he ran it by double clicking the .reg file in a 32 bit instance of explorer. Whichever it is, it still sounds like he's getting the 32 bit emulation redirection.

I have my own PromptHere you can download here:
Hotkeys

It has the ahk source code. You can download AHK_L and compile in 64 bit if you want. Anyway, it doesn't rely on the registry since it doesn't do context menu. It uses a hotkey. Select a folder and hit the hotkey.

Uses optional blur window on W7.

Sorry, I was thinking of the process for the command prompt for "Open elevated command window here".

I understand. I was just thinking if the system passed him a 32 bit explorer it might reflect into the 32 bit emulation. Whereas if he invoked it via a 64 bit command prompt it shouldn't. But it's all just speculation. :) I just suggested my alternative since it doesn't depend on the registry. It just uses a clipboard macro to get the name(s) of the folder(s). :)

So REG isn't working
start a CMD which is not working
cd \
REG ->this fails
cd C:\Windows\system32
REG

does that work?

Kaktussoft said:

So REG isn't working
start a CMD which is not working
cd \
REG ->this fails
cd C:\Windows\system32
REG
does that work?

Please see the screen cap, Kaktussoft -



As you can see, REG works (as in it is recognized as a command) in C:\Windows\System32 and in C:\Windows\SysWOW64, but not anywhere else, it seems.

your path is C:\BatCom\;C:\Programs\SscePortable;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windo ws\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\C ommon Files\Lenovo;C:\Program Files (x86)\Common Files\Ulead Systems\MPEG;C:\Program Files x86)\Windows Live\Shared;C:\SWTOOLS\ReadyApps;C:\Program Files (x86)\ Intel\Services\IPT\;

Maybe a file called reg.exe, reg.com, reg.bat is in C:\BatCom\ or C:\Programs\SscePortable? please check that

fwcetus said:

echo %path%
C:\BatCom\;C:\Programs\SscePortable;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windo ws\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\C ommon Files\Lenovo;C:\Program Files (x86)\Common Files\Ulead Systems\MPEG;C:\Program Files x86)\Windows Live\Shared;C:\SWTOOLS\ReadyApps;C:\Program Files (x86)\ Intel\Services\IPT\;

C:\Program Files x86)\Windows Live\Shared
should be C:\Program Files (x86)\Windows Live\Shared

Typing error?

C:\Programs\SscePortable => what program is that? Is it realy in c:\programs? or C:\Program Files (x86)?

C:\BatCom\ => why slash at the end? (it doesn't matter I assume)

Kaktussoft said:

your path is C:\BatCom\;C:\Programs\SscePortable;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windo ws\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\C ommon Files\Lenovo;C:\Program Files (x86)\Common Files\Ulead Systems\MPEG;C:\Program Files x86)\Windows Live\Shared;C:\SWTOOLS\ReadyApps;C:\Program Files (x86)\ Intel\Services\IPT\;

Maybe a file called reg.exe, reg.com, reg.bat is in C:\BatCom\ or C:\Programs\SscePortable? please check that

C:\BatCom\ is most likely the problem!! Put on the end of path.

So cut C:\BatCom\; from start and paste it on end. Press OK multiple times.
Now start cmd again, did path change?

post results
How To Add/Edit Environment Variables in Windows 7 | Windows7hacker