Latest Windows 10 build makes PowerShell default command line

Quote:

---

30 year old cmd.exe usurped by PowerShell in the Insider Preview Build 14971 for PC.

---

Read more.

Oddly, I still haven't defaulted to PowerShell, although cannot think of any reason why I haven't....(apart from possibly preferring black over blue for a CLI :P )

IIRC, there is a GPO to make it the default as well.

Never felt the need to migrate, Command Prompt has always done what I've needed it to do, I like to keep things as simple as possible. As of yet I've not been required to engage in any component that is only PS based.

Taken from the known issues list:

Double-clicking on an Excel document to open it from File Explorer will crash Microsoft Excel. The workaround is to open the document from within Excel.

What a joke...

Quote:

---

Originally Posted by Airwave

Taken from the known issues list:

Double-clicking on an Excel document to open it from File Explorer will crash Microsoft Excel. The workaround is to open the document from within Excel.

What a joke...

---

Beta preview software often is!

I am reminded of this classic:

https://github.com/MrMEEE/bumblebee-...ned/issues/123

Think I'd be more impressed if they made bash (especially the Cygwin version) the default.

Linux bigotry aside though, I've heard good things about Powershell - to the point of having 'find a decent tutorial or intro' on my tech to-do list.

Anything that modernises/replaces that God awful DOS relic of a shell is to be welcomed.

Microsoft need to add a quick way to open it.

Start, run, ps
-for example.

CMD is 6 keys from your fingertips.

Quote:

---

Originally Posted by bledd

Microsoft need to add a quick way to open it.

Start, run, ps
-for example.

CMD is 6 keys from your fingertips.

---

CMD is:

Winkey +x followed by C or A (if you want it evevated)

Once CMD has been replaced by PowerShell, it takes the same shortcuts.

Bah, they've only just added resizeable command prompt and now they want to remove it!

I thought the command prompt has always been resizable, at least i think i remember doing it with W95.

Quote:

---

Originally Posted by Corky34

I thought the command prompt has always been resizable, at least i think i remember doing it with W95.

---

It was a faff, normally having to set the column and row sizes (like and old DOS CON command!).....now it can be re-sized like any other window.

Right click pastes your copy/paste buffer now as well.....

Quote:

---

Originally Posted by bledd

Microsoft need to add a quick way to open it. ...

---

Right click the windows logo. Currently both Command Prompt and Command Prompt (Admin) are there, but I assume once PS is the default it'll replace them in the start context menu.

Alternatively, Win key then start typing "powershell". By the time I get to "po" both my Server 2012 and Win 10 Enterprise VMs have already made powershell the default option, at which point hitting return will open it. Depending on your most used programs I suspect "p" alone might do the job...

Quote:

---

Originally Posted by shaithis

It was a faff, normally having to set the column and row sizes (like and old DOS CON command!)....

---

Heh, I was responsible for the time settings going wonky on all of my uni's lab computers once just because I preferred DOS EDIT to any other text editor available on Win NT 4 (it kept my hanging indents). Of course, the only way to run it was from a command prompt. The network admins had removed all the links to command.com, but hadn't disabled it, so it was easy enough for me to just run command.com.

Then one day I got spotted using edit by one of the admins, who came over and had a - perfectly polite and reasonable - chat to me about how and why I was using EDIT from command.com. A couple of days later standard user accounts were denied permission to run command.com, which would've been fine if the clocks on every computer weren't set at log in by a processes running in command.com as the logged in user.... ;)