Recommended Posts

Annoyed that microsoft are forcing you to use the annoying take-over-my-whole-damn-screen poxy powershell instead of allowing you to use command prompt when holding shift and right clicking in explorer windows? No problem, found a fix for it that actually works without having to add another context menu.

First: what doesn't work - replacing the powershell exe with the command prompt exe... I don't have a clue what they've done, but if you try this the command prompt icon changes to a powershell icon and if you run it, it opens a half command prompt half powershell window which is literally the worse of both combined, it's got the obnoxious size of powershell with the massive font and the command prompt messages are all broken. So if you rename a file powershell (I haven't tried in other folders) it will make your life more of a misery, they're really intent on making your life as difficult as possible.

 

Luckily, there's a solution, go to start, type in regedit, right click and run as administrator. Navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\background\shell\Powershell and right click on the command folder, click permissions. Click Advanced and near the top you'll see it's owned by trusted installer or system, whatever, click 'change' > advanced > find all and find your username or the users group, click OK then check the 'take permissions of sub objects' checkbox and click OK again. In the top half of the window, either add your user account to the list or go to 'users' and give them full permission, click OK. Now click on the command folder (optionally backup the value of (Default) if you ever want powershell back but I can't fathom any possible reason you'd ever want to do that) and double click the (Default) value, replace the 'powershell.exe' command at the front with 'cmd.exe' and click OK. Test out that when you shift-right click and select 'open powershell window' you now get a lovely small command prompt window - glorious. I haven't found a way to replace the text in the context menu but if I'm honest, I don't care, command is back and that's all that matters.

You can optionally change the registry key permission back to system or trusted installer if you want to prevent other users tampering with it but that's up to you.

 

I can't wait to see what happens with the next grand update, are they going to force open edge whenever you click your own browser's icon? No doubt it'll be something complete stupid like that.

Right Click Taskbar, Taskbar Settings, change slider for "Replace Command Prompt with Windows Powershell".

 

To change it on your Right click start menu

  On 16/04/2017 at 19:23, xendrome said:

Right Click Taskbar, Taskbar Settings, change slider for "Replace Command Prompt with Windows Powershell".

 

To change it on your Right click start menu

Expand  

 

  On 16/04/2017 at 19:47, Anibal P said:

 

Expand  

snipped, here's what neither of you have done:

  • ☐ Checked the windows 10 creators update changelog
  • ☐ Searched on the internet for this problem including 'creators update' in the search term
  • ☐ Tested out the method you described
  • ☐ Realised you're both flat out wrong.

But of course no, leave it up to me to show you:

neowin_idiot.thumb.png.494fd3abdb0be8a4d873b6382482567a.png

Oh what's that?

  • ☑ Windows 10 creators update
  • ☑ Use powershell instead of command prompt option DISABLED
  • ☑ Right click context menu showing 'open in powershell'
  • ☑ The window opened is powershell
  • ☑ The text no longer mentions context menu and just mentions start menu

 

Go and look up things before you post or at least try them before posting completely wrong, outdated information.

 

 

The powershell takes over whole screen bit is rather dramatic, drama queen dramatic. Resize it and it will remember the setting. If it takes over your whole screen, it is because you allow it to happen.

 

 

 

  On 16/04/2017 at 21:25, adrynalyne said:

 

 

The powershell takes over whole screen bit is rather dramatic, drama queen dramatic. Resize it and it will remember the setting. If it takes over your whole screen, it is because you allow it to happen.

 

 

 

Expand  

Doesn't work here, resizing powershell, closing it and reopening it opens at the default size. Also changing the options in default has no effect, setting the size from 120x60 to 60x20 opens it at the exact same size.

  On 16/04/2017 at 21:32, n_K said:

Doesn't work here, resizing powershell, closing it and reopening it opens at the default size. Also changing the options in default has no effect, setting the size from 120x60 to 60x20 opens it at the exact same size.

Expand  

Odd, it works here.

  On 16/04/2017 at 21:32, n_K said:

Doesn't work here, resizing powershell, closing it and reopening it opens at the default size. Also changing the options in default has no effect, setting the size from 120x60 to 60x20 opens it at the exact same size.

Expand  

Try this.  Resize it with your mouse. Open Properties. Note the changes in layout. Click ok, close, and try reopening it. Its saving for me.

 

Note: this is location dependent. Launching it from different locations can have different sizes.

  On 16/04/2017 at 21:38, adrynalyne said:

Try this.  Resize it with your mouse. Open Properties. Note the changes in layout. Click ok, close, and try reopening it. Its saving for me.

 

Note: this is location dependent. Launching it from different locations can have different sizes.

Expand  

Ah nice that works, only seems to work in the properties section, I've just noticed the defaults options was having an effect and changed the size of my command prompts but not powershell.

Just another note to say that Powershell, by default, isn't full screen.  I've got lots of lab boxes and use powershell all the time (non customized) and I've never seen a fullscreen powershell.  (and having said this, while I sympathize with the poster's dilemma, wouldn't recommend a reg change to fix...)

 

Also if it's oversized, it could be a scaling issue derived from the desktop settings.

 

Curious what is actually broken in the Powershell window, as it should just launch all the same CMD prompt files.  If not, there's probably a path issue, which again, I've not seen in any vanilla setting.

 

Powershell is awesome, and I've seriously abandoned the command prompt... because this really replaces it.  There are a few commands that simply don't work, but mostly because they are basically part of CMD.EXE literally (for example: "ver"), and can be scripted into Powershell.

  On 16/04/2017 at 20:02, n_K said:

 

snipped, here's what neither of you have done:

  • ☐ Checked the windows 10 creators update changelog
  • ☐ Searched on the internet for this problem including 'creators update' in the search term
  • ☐ Tested out the method you described
  • ☐ Realised you're both flat out wrong.

But of course no, leave it up to me to show you:

neowin_idiot.thumb.png.494fd3abdb0be8a4d873b6382482567a.png

Oh what's that?

  • ☑ Windows 10 creators update
  • ☑ Use powershell instead of command prompt option DISABLED
  • ☑ Right click context menu showing 'open in powershell'
  • ☑ The window opened is powershell
  • ☑ The text no longer mentions context menu and just mentions start menu

 

Go and look up things before you post or at least try them before posting completely wrong, outdated information.

Expand  

Just to verify, the method that is listed does work for me, on Creators update.

The information is not outdated or wrong.  it is that you do not have it operation that way.  there is a rather large difference with that.

 

  On 17/04/2017 at 00:16, Clirion said:

Just to verify, the method that is listed does work for me, on Creators update.

The information is not outdated or wrong.  it is that you do not have it operation that way.  there is a rather large difference with that.

 

Expand  

I've tested on an upgraded win 10 pro N system and a fresh install win 10 pro N system and the taskbar settings works on neither for the right click context menu. There's threads out there also saying the same thing, that you cannot get command prompt back in the shift-right click context menu unless you edit the registry, see http://www.winhelponline.com/blog/cmd-here-windows-10-context-menu-add/ and the comments underneath. If it works for you then I'd say it's likely your system that's the odd one out.

  On 16/04/2017 at 21:54, mram said:

Just another note to say that Powershell, by default, isn't full screen.  I've got lots of lab boxes and use powershell all the time (non customized) and I've never seen a fullscreen powershell.  (and having said this, while I sympathize with the poster's dilemma, wouldn't recommend a reg change to fix...)

 

Also if it's oversized, it could be a scaling issue derived from the desktop settings.

 

Curious what is actually broken in the Powershell window, as it should just launch all the same CMD prompt files.  If not, there's probably a path issue, which again, I've not seen in any vanilla setting.

 

Powershell is awesome, and I've seriously abandoned the command prompt... because this really replaces it.  There are a few commands that simply don't work, but mostly because they are basically part of CMD.EXE literally (for example: "ver"), and can be scripted into Powershell.

Expand  

It's never been full screen but it's default size on my system is about 80-90% of the screen, by editing the properties as adrynalyne suggested I got it smaller which I would have thought the defaults setting would do but instead the defaults setting changes command prompt.

I'm currently running W10 on a mechanical hard drive, the difference between opening command prompt and powershell at boot is about 1/2 a second to 15 seconds. After a while retesting opens command prompt in about the same time but powershell still takes 2-3 seconds longer to open and close. It might be nothing to the majority of people but to me it's just annoying.

  On 16/04/2017 at 20:02, n_K said:

 

snipped, here's what neither of you have done:

But of course no, leave it up to me to show you:

 

Oh what's that?

 

Go and look up things before you post or at least try them before posting completely wrong, outdated information.

Expand  

Umm I was just stating how to change it on the right click start menu. Read things before you post.

  On 16/04/2017 at 21:25, adrynalyne said:

 

 

The powershell takes over whole screen bit is rather dramatic, drama queen dramatic. Resize it and it will remember the setting. If it takes over your whole screen, it is because you allow it to happen.

 

 

 

Expand  

Maybe is he in tablet mode... then I could see it doing such a thing.

  On 17/04/2017 at 12:51, Riggers said:

Just editing the setting works for all the systems iv`e tried it on...

 

2.thumb.png.989dde549d8530ec10654692df670268.png

Expand  

You right clicked the start button, so yes. That's not what he was asking for. 

  On 17/04/2017 at 13:43, Raa said:

Now if only there was an easy option like that to revert to the classic Control Panel. ;)

 

Thanks for that tip though - hadn't gone looking, but it was one of my "oh dear" points.

Expand  

Start, type "Control Panel"

  On 17/04/2017 at 13:29, Riggers said:

But he said xendrome was wrong, i was just clarifying that part!

Expand  

Xendrome wasn't wrong in what he said, but it didn't address what he asked. Nor did you. I too, initially misunderstood. 

 

Just clarifying ;)

 

This topic is now closed to further replies.