Open command window here - Add in Windows 10  

Page 2 of 6 FirstFirst 1234 ... LastLast

  1. hexaae
    Posts : 181
    Windows 10 Pro x64
       New #10

    Brink said:
    Hello @hexaae, :)

    I haven't found a way to add it back to the File menu yet, but I will keep an eye out.
    Mmmh, I tried to add for the newly created 3 cmd2 entries in the registry:
    ShowBasedOnVelocityId (DWORD32): <num>
    (with <num> based on the corresponding value originally under the original 3 cmd HideBasedOnVelocityId) but nothing changed.

    I tried the trick on cmd2 entries since I can't modify original keys (owner is usual TrustedInstaller...)
    HKEY_CLASSES_ROOT\Directory\Background\shell\cmd\HideBasedOnVelocityId
    HKEY_CLASSES_ROOT\Directory\shell\cmd\HideBasedOnVelocityId
    HKEY_CLASSES_ROOT\Drive\shell\cmd\HideBasedOnVelocityId

    ...but I think this is the right direction to get back the items in File menu
    We're close to solution...
      My Computer
    Quote Quote

  3. hexaae
    Posts : 181
    Windows 10 Pro x64
       New #11

    Just tried with SYSTEM rights to edit those keys:
    HKEY_CLASSES_ROOT\Directory\Background\shell\cmd\HideBasedOnVelocityId
    HKEY_CLASSES_ROOT\Directory\shell\cmd\HideBasedOnVelocityId
    HKEY_CLASSES_ROOT\Drive\shell\cmd\HideBasedOnVelocityId
    changing HideBasedOnVelocityId -> ShowBasedOnVelocityId, but didn't re-add the cmd prompt back in File menu
    They only re-enabled cmd prompt on Shift+RMB just like your tutorial for "cmd2"...
      My Computer
    Quote Quote

  4. Brink
    Posts : 68,881
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       New #12

    JeffF73 said:
    Sorry I didn't catch the Path/Location in regedit. If it ever happens again I will post the results.
    I figured out what caused this issue I had though. I used "Winaero Tweaker" and the Add_Open_command_window_here.reg that you have above at the same time.
    The "Winaero Tweaker" added the new path/location settings in registry which caused an issue with my Start10, your posted removal.reg above removed the other options from the desktop/folder context menus. But Even though I used your removal.reg the to remove it. The "Winaero Tweaker" kept it stuck in the Start10 context menu which caused an issue with my right side folders context menu and only opened command prompt when even while left clicking because it made it an active link. It's better to only use one or the other I have found out LOL. now with Winaero Tweakers Open Command Prompt Here removed as well as registry key's the Start10 doesn't have it at all now even with your Add_Open_command_window_here.reg applied.
    Great news Jeff. Thank you for posting back with your findings. :)
      My Computers
    Quote Quote

  5. Brink
    Posts : 68,881
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       New #13

    hexaae said:
    Just tried with SYSTEM rights to edit those keys:
    HKEY_CLASSES_ROOT\Directory\Background\shell\cmd\HideBasedOnVelocityId
    HKEY_CLASSES_ROOT\Directory\shell\cmd\HideBasedOnVelocityId
    HKEY_CLASSES_ROOT\Drive\shell\cmd\HideBasedOnVelocityId
    changing HideBasedOnVelocityId -> ShowBasedOnVelocityId, but didn't re-add the cmd prompt back in File menu
    They only re-enabled cmd prompt on Shift+RMB just like your tutorial for "cmd2"...
    It was a worth a try.

    I added "cmd2" to avoid folks from having to take ownership of the original "cmd" key first. It's just a workaround to make it easier to apply.
      My Computers
    Quote Quote

  7. TG2
    Posts : 13
    Win 10x64 Pro
       New #14

    Brink said:
    It was a worth a try.
    Does this mean you've given up hope? Maybe obi-wan can help? can we find an obi-wan for this?


    Seriously though .. adding myself to this thread in case you do find one .. I'm not averse to having *both* CMD & PowerShell ... I just don't need power shell and like the muscle memory of ALT+F C (or arrow down and enter). If I had a million dollars.. I'd be leaving thank yous at a lot of sites, TenForums would get at least tree fiddy. O
      My Computer
    Quote Quote

  8. Brink
    Posts : 68,881
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       New #15

    Hello TG2, :)

    The tutorial has already been updated to use "cmd2".

    You can use the tutorial below to remove from the Open PowerShell window here context menu.

    Open PowerShell window here context menu - Add in Windows 10 Windows 10 Customization Tutorials
      My Computers
    Quote Quote

  9. TG2
    Posts : 13
    Win 10x64 Pro
       New #16

    Brink said:
    The tutorial has already been updated to use "cmd2".
    Yeah, thats Right Click Context .. the 2nd or 3rd post down in the beginning of the thread asked about adding or changing in the *File* menu of explorer (er.. "FileExplorer" as it is in the registry)


    I should've been more specific than the "Alt+F" for File menu. Sorry

    And I don't begrudge people that like or want powershell .. just that I don't need it most of the time, I need command prompt.

    All I can see is microsoft's insistence on forcing garbage changes on people ... I mean seriously .. do you want the average 'just-to-dangerous-user' getting into power shell and going off half cocked toward something they thought they understood but really didn't?

    < sigh >
      My Computer
    Quote Quote

  10. Brink
    Posts : 68,881
    64-bit Windows 11 Pro for Workstations
    Thread Starter
       New #17

    Yeah, I still haven't been able to find a way to modify the File (Alt+F) menu yet.
      My Computers
    Quote Quote

  11. hexaae
    Posts : 181
    Windows 10 Pro x64
       New #18

    I've found you can simply enter "cmd" in PowerShell to run a (nested) MS-DOS prompt session. Also fonts colors will turn to white to notify this. Best workaround for me ATM.

    P.S.
    You can quit MS-DOS session and go back to PowerShell with "exit" of course... Or quick-quit this shell window with Alt+F4.
    Last edited by hexaae; 11 Jul 2017 at 04:16.
      My Computer
    Quote Quote

  13. f14tomcat
    Posts : 56,825
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       New #19

    hexaae said:
    I've found you can simply enter "cmd" in PowerShell to run a (nested) MS-DOS prompt session. Also fonts colors will turn to white to notify this. Best workaround for me ATM.

    P.S.
    You can quit MS-DOS session and go back to PowerShell with "exit" of course...
    WIN Key + R, CMD, enter.

    That's never going away......
      My Computers
    Quote Quote

 

Tutorial Categories

Open command window here - Add in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


  Related Discussions
How to Add "Open command window here as administrator" context menu in Windows 10 A command prompt is an entry point for typing computer commands in the Command Prompt window. By typing commands at the command prompt, you can perform tasks on...
295141 Hi, Is anyone else seeing this? After searching from the Taskbar and opening the Administrator Command Prompt this is what Ive lately started to see. Im wondering if its just something that happens in 1909. I have seen it before and it is...
General Tips Open Command Prompt in Windows 10
in Tutorials

How to Open a Command Prompt in Windows 10 A command prompt is an entry point for typing computer commands in the Command Prompt window. By typing commands at the command prompt, you can perform tasks on your computer without using the Windows...
Before the upgrade to v1909, a batch file that would save a spreadsheet to two locations, then close Excel, used to open a 'DOS' window that was unobtrusively small. Now, the window stretches from the bottom to the top of the screen. It does not...
I want to use the command line to open the "Custom sizing options" window in Windows 10, please view the image, thank you. 99228
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 01:22.
Find Us




Windows 10 Forums