If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
"Open command window here" not working
Windows 10 1709 build 16299.309 (64-bit); HP-15 f039 Rt-click or Shift+Rt-click - Open command window here - (popup): quote This file does not have a program associated with it for performing this action. Please install a program or, if one is already installed, create an association in the Default Programs control panel. /quote My main issue right now is that Windows can no longer recognize an ADB command. SFC /scannow found errors and repaired some but it made no difference with "Open command window here" misbehavior. Any troubleshooting pointers greatly appreciated. Thanks. |
Ads |
#2
|
|||
|
|||
"Open command window here" not working
M.L. wrote:
Windows 10 1709 build 16299.309 (64-bit); HP-15 f039 Rt-click or Shift+Rt-click - Open command window here - (popup): quote This file does not have a program associated with it for performing this action. Please install a program or, if one is already installed, create an association in the Default Programs control panel. /quote My main issue right now is that Windows can no longer recognize an ADB command. SFC /scannow found errors and repaired some but it made no difference with "Open command window here" misbehavior. Any troubleshooting pointers greatly appreciated. Thanks. Use Nirsoft's ShellMenuView to see those object extensions. You should see 3 entries for "Open command &window here" (the "&" means to underline the next character for use as a shortcut key). The 3 entries that I see are for different object types: Directory/Background Directory Drive You cannot open a command prompt on a file since that is not a space for other objects (files or subfolders). When you right-click on an entry in ShellMenuView and select Properties, you will see the handler for that object handler: where is the handler (program) executable, the command line to which the argument is passed to the handler, and even the registry key under which this handler is defined. When I looked, each of the above object handlers were defined as follows: Filename: C:\Windows\system32\cmd.exe Command: cmd.exe /s /k pushd "%V" Do you have a copy of cmd.exe under the system32 folder? If you use the Start-Run menu or use Winkey+R and just enter "cmd.exe" (no path to file and no arguments), does a command shell (aka command prompt) open up in its own window? https://www.howtogeek.com/235101/10-...in-windows-10/ ADB? Hmm, that could be lots of different things. See: https://www.acronymfinder.com/ADB.html If you asking about entering commands for Android Debugging Bridge (to communicate from your PC to a smartphone), is Windows 10 on a desktop PC or on a smartphone or tablet or other mobile device? If on a mobile device, did you ever enable Debugging Mode under Developer options on the smartphone? Did you ever install the ADB driver on your desktop PC? |
#3
|
|||
|
|||
"Open command window here" not working
Windows 10 1709 build 16299.309 (64-bit); HP-15 f039 Rt-click or Shift+Rt-click - Open command window here - (popup): quote This file does not have a program associated with it for performing this action. Please install a program or, if one is already installed, create an association in the Default Programs control panel. /quote My main issue right now is that Windows can no longer recognize an ADB command. SFC /scannow found errors and repaired some but it made no difference with "Open command window here" misbehavior. Any troubleshooting pointers greatly appreciated. Thanks. Use Nirsoft's ShellMenuView to see those object extensions. You should see 3 entries for "Open command &window here" (the "&" means to underline the next character for use as a shortcut key). The 3 entries that I see are for different object types: Directory/Background Directory Drive You cannot open a command prompt on a file since that is not a space for other objects (files or subfolders). When you right-click on an entry in ShellMenuView and select Properties, you will see the handler for that object handler: where is the handler (program) executable, the command line to which the argument is passed to the handler, and even the registry key under which this handler is defined. When I looked, each of the above object handlers were defined as follows: Filename: C:\Windows\system32\cmd.exe Command: cmd.exe /s /k pushd "%V" Do you have a copy of cmd.exe under the system32 folder? If you use the Start-Run menu or use Winkey+R and just enter "cmd.exe" (no path to file and no arguments), does a command shell (aka command prompt) open up in its own window? https://www.howtogeek.com/235101/10-...in-windows-10/ ADB? Hmm, that could be lots of different things. See: https://www.acronymfinder.com/ADB.html If you asking about entering commands for Android Debugging Bridge (to communicate from your PC to a smartphone), is Windows 10 on a desktop PC or on a smartphone or tablet or other mobile device? If on a mobile device, did you ever enable Debugging Mode under Developer options on the smartphone? Did you ever install the ADB driver on your desktop PC? ADB = Android Debugging Bridge I want to clarify that I had no problem using cmd.exe via the Run command, followed by using the "cd" command to navigate to a specific directory. The issue is that using "Open command window here" didn't work. Your Nirsoft recommendation led me to find a reg file download to disable and re-enable "Open command window here" The command worked as expected after it was re-enabled. Thank you so much for your reply. https://www.tenforums.com/tutorials/...dows-10-a.html |
#4
|
|||
|
|||
"Open command window here" not working
Any troubleshooting pointers greatly appreciated. Thanks. Create a new Windows profile and try from that new account. If it works then you know your old profile is polluted withy your sperms. By the way it is "OpenPowershell Window Here" in Windows 10 that is correctly configured and maintained!!! This is the case even if you have configured to open cmd prompt in Settings. Thank you for your reply. The latest Windows 10 update only allows either a Powershell command or a Command Prompt entry in the Start menu, not both. I was able to resolve the issue by downloading reg files to disable my apparently corrupt "Open command window here" entry and then re-enable it. It's all working fine now. command prompt reg downloads: https://www.tenforums.com/tutorials/...dows-10-a.html |
Thread Tools | |
Display Modes | Rate This Thread |
|
|