18 ms·
Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build
- 6u54wuwu5w 10y agoSo, while I applaud this, I am concerned about the startup time of ps as compared to the old command prompt. Has it been improved recently?
- louhike 10y agoIt's better but it's still slower than CMD on my computers.
- algorithmsRcool 10y agoIn particular if you have left the prompt window untouched for a few hours and it has been paged out. Just pressing <tab> to complete a file name will hang for 3-6 seconds on my computer while PS wakes back up. CMD is always instantaneous. I realize that PS is doing a lot more work to match commands but sometimes simple is all that is needed.
- richard_todd 10y agoFunny, that was my first thought as well. Sometimes I start cmd.exe instead of powershell on rotating-disk machines because of the startup time. On SSDs I find the startup time is negligible.
- Aldo_MX 10y agoThat's my biggest concern, I actively avoid PS just because I can't tolerate its startup time.
- zamalek 10y agoStill slower than cmd, fast enough that I'm actively trying to unlearn the cmd muscle memory.
- JeffreySnover 10y agoMajor improvements in V5. Even more in V5.1 (which ships with WS2016). But still slower than CMD. CMD starts very quickly but then you have CMD. :-) Jeffrey Snover [MSFT]
- FLGMwt 10y ago"Typing cmd in the run dialog will launch PowerShell as well" What? I'm a big PowerShell fan, but I see the need to keep cmd around for a while. Clobbering it before it's phased out seems problematic.
- freedrock87 10y agoYou can run any command from CMD in Powershell
- viraptor 10y agoBut are all cmd commands portable verbatim to powershell? With all the options / special characters? (I don't know the answer, but https://en.wikipedia.org/wiki/PowerShell#Comparison_of_cmdlets_with_similar_commands https://en.wikipedia.org/wiki/PowerShell#Comparison_of_cmdle... lists quite a few missing commands, including "talkkill" and "find") With the amount of online posts that tell you "to achieve X, open command prompt and run ...", it would be a bad idea to break any of them that go beyond a simple command. (so for example any "FOR ..." lines)
- janwillemb 10y agoTalkkill seems like a very useful feature to me ;)
- orbitingpluto 10y agoThere can be several aliases for a single command. ls=dir=gci="Get-ChildItem" But you can't run just run "dir /s". You'd have to say "Get-ChildItem -Recurse" which can be shortened to "dir -Recurse" which can be shortened to "dir -r". When scripting, you try to use the longform versions. With one-liners, you just sort of fall into whatever paradigm you were previously accustomed to for your first argument.
- hobarrera 10y agoSuch basic commands are actually CamelCase? It must be a pain for those with no short-aliases.
- hugja 10y agoI'm probably wrong, but can you not type "ps" into CMD and get the PowerShell prompt? If so, can you do it the other way around as well?
- lini 10y agoIt's actually 'powershell' and not just 'ps', but you are right. Typing 'powershell' gets you to PS and typing 'cmd' gets you the command prompt.
- algorithmsRcool 10y agoyou can run "powershell" from a CMD prompt and "cmd" from a powershell prompt. You can also nest prompts to switch context between them.
- yoz-y 10y agoYou can also `start /b cmd` for some very interesting results. I still have not understood why this works this way.
- godzillabrennus 10y agoJust another reason to stay away from Windows as a platform. Windows 10 is a moving target if you are trying to work with it.
- poizan42 10y agoHow is that any different from Linux distributions camping their default shell? Like back when debian changed their default shell to dash I don't remember anyone saying you should stay away from debian, even though it broke a lot of existing scripts.
- shostack 10y agoDid you have a choice to upgrade? Could you reinstall the old version of you wanted? Windows has stripped that power from users.
- viraptor 10y agoThat's a bit different. The change only exposed that some scripts were already broken and worked by accident. Specifying that your script should be run with #!/bin/sh and then using bash syntax is what broke them. It's a bit like naming your files something.c, writing the code in C++ and compiling with `cc` just because `cc` happened to be linked to `c++` on your system. It will work for you, but don't be surprised when you distribute the source and people have problems using it. Scripts that used #!/bin/bash still worked, scripts that actually used only sh syntax and #!/bin/sh still worked.
- pawadu 10y agoSo basically instead of doing dir C:\ I have to learn to type List-Directory-With-Files Drive=C Folder=/ (made up example, but you get the point)
- Tarean 10y agoNo, dir `c:\ works` just fine. It is a short version for Get-ChildItem -Directory C:/
- Senji 10y agols c:\ or gci c:\
- taspeotis 10y agohttp://imgur.com/kDQVBZw http://imgur.com/kDQVBZw
- pawadu 10y agoSure, go ahead, ruin my joke :) More seriously, how many seconds did it took for the PS to answer to that command?
- taspeotis 10y agoMeasure-Command {dir C:\} TotalMilliseconds : 2.9708 Measure-Command {Get-ChildItem "C:\"} TotalMilliseconds : 2.4161
- pritambaral 10y agoCompare it with cmd.exe's dir
- taspeotis 10y agoI have had a quick look through here [1] and most of the answers involve timing precision of two significant digits. By that metric, PowerShell's 2.4ms clocks in at 0.00 seconds. Which means cmd.exe (at a precision of two significant digits) can't beat it. [1] http://stackoverflow.com/questions/673523/how-to-measure-execution-time-of-command-in-windows-command-line http://stackoverflow.com/questions/673523/how-to-measure-exe...
- chrsw 10y agoHopefully one day Bash will be the default Windows CLI.
- BrandonBradley 10y agoMicrosoft has made some good changes, but don't get your hopes up! :)
- neovive 10y agoOr maybe a compatibility layer, where they integrate the most common bash commands and Unix utilities. I prefer Git Bash when on Windows for this reason.
- dtougas 10y agoThere is a compatibility layer now, it just happens to be a complete Ubuntu environment.
- marcosdumay 10y agoMaybe an year or two after all Linux users migrate their to some idiom of Python.
- dagaci 10y agoPath of the course perhaps. After 30+ years of fighting a what was always a "rear guard action" against the prevailing dominant Unix customs and methods Nadella has switched Microsoft and Windows into a full-on conformist mode by removing the immediate -> monetization of the OS and thus the need to be "different". It would not surprise me in a few years to come, to find even sooner than expected that "Windows" had become another variant of Unix in effect if not entirely in fact.
- curt15 10y agoBash has its warts too. Treating everything as strings can cause headaches when filenames have spaces. As a long-time Linux user who recently learned some powershell, I find Bash rather primitive after getting accustomed to an environment where everything is an object. I wonder how feasible it would be to build a powershell-like environment for Linux on top of Python.
- mauvehaus 10y agoThat's nice. Can you pipe binary data without powershell corrupting it, or is that now a feature? https://brianreiter.org/2010/01/29/powershells-object-pipeline-corrupts-piped-binary-data/ https://brianreiter.org/2010/01/29/powershells-object-pipeli...
- gfody 10y agoRelated, running something like decrypt hugefile.dat | encode outfile.dat will usually result in powershell using up all your system ram and crashing.
- brazzledazzle 10y agoOn a somewhat related note, one of PowerShell's biggest weaknesses is memory utilization. And since they make it so simple to pass around hefty object collections it tends to bite you in the ass early on. Particularly when you're using cmdlets. When doing real scripting that actually needs to be run as a job I am surprised when I can get away with cmdlets and don't need to manage .net APIs/objects directly. Especially third party cmdlets. One performance tip I picked up early on: If you're passing around large object sets you need to operate on try to keep them in a pipeline. Populating a variable and interacting with it is arguably more readable and maintainable, especially for junior people, but it has a heavy cost in terms of memory. That said every version of posh is better than the last so I may be wrong or overestimating the impact for the newest versions. YMMV, don't believe everything you read on the internet, etc.
- youdontknowtho 10y agoThat's great advice, man. Cheers.
- JeffreySnover 10y agoThat is a good tip. There are certain product teams that produced ENORMOUS objects and your suggestion helps when dealing with that. Jeffrey Snover [MSFT]
- ungzd 10y agoHaving repl of some strange CLR language as primary shell is weird but having port of DOS shell is weird too.
- baq 10y agoif you put it this way, having a repl of an organically grown language that can barely do arithmetic is weird, too.
- dvh 10y agoBtw did anyone noticed that in windows 10 you can resize cmd.exe to more than 80 characters width! When I first saw it I almost cried.
- rhapsodic 10y agoI've been able to do that in versions of Windows going back as far as I can remember.
- cmdrfred 10y agoThey made the option easier to find.
- herbst 10y agoCorrect me if i am wrong, but all i remember is you could edit the width somewhere in the options. But there was no way to change the width _on the fly_ (assuming thats something it does now)
- beagle3 10y agoOlder versions could resize the window with a drag, but the underlying buffer required a menu option, which was very awkward. In Win10, you can resize the buffer with a drag as well.
- ihalip 10y agoI don't remember ever not having that feature, so it must be around ever since XP. Right click window -> Properties -> Layout.
- sapphire_tomb 10y agoOP means you can drag the window wider - no need to alter properties anywhere ;)
- krylon 10y agoMy work laptop still runs Windows 7 - and will for the foreseeable future - but that is one of the things that make me curious about Windows 10. It is, of course, easy to ridicule Microsoft for how long it took them to change this, but I think better late than never. (On older versions of Windows, ConEmu[1] does that, too, but it's third-party software, of course. It also supports tabs!) [1] https://conemu.github.io/ https://conemu.github.io/
- Diti 10y agoSomething that irks me is how PowerShell’s default aliases take precedence over binaries in the PATH. To be able to use the GNU utils, you have to put this in your profile.ps1: Remove-Item Alias:cat Remove-Item Alias:cp Remove-Item Alias:curl Remove-Item Alias:echo Remove-Item Alias:ls Remove-Item Alias:man Remove-Item Alias:mv Remove-Item Alias:pwd Remove-Item Alias:rm Remove-Item Alias:wget
- mhd 10y agoHow would an alias work otherwise? That's pretty much the way it behaves in Unix, too (e.g. 'ls' in most default configs). Although I'd still consider curl/wget to be specific tools and not generic commands, so emulating them seems a bit weird.
- SloopJon 10y agoThe point is that they're defined by default. See this story for more background: https://news.ycombinator.com/item?id=12319670 https://news.ycombinator.com/item?id=12319670 Edit: the RFC intended to address the curl author's issue was rejected. https://github.com/PowerShell/PowerShell-RFC/blob/master/X-Rejected/RFC0007-Weak-Aliases.md https://github.com/PowerShell/PowerShell-RFC/blob/master/X-R...
- emodendroket 10y agoYeah, because it would represent a breaking change.
- AimHere 10y agoThere are use-cases where globally removing aliases isn't an option (e.g. scripting for use on a machine that isn't yours). For those, it's also possible to evade the aliasing just by explicitly appending the .exe onto the command. 'pwd.exe' gets you the GNU version.
- marcosdumay 10y ago
- chiph 10y agoUh-Oh. Work has many cmd scripts in use. They'll all have to be tested under PS now.
- ygra 10y agoNo, batch files won't magically get run by PowerShell (and in fact cannot, except for very trivial stuff).
- globalgobble 10y agoWhy ? Because some linux zealots think it's the best option ? Laughable.
- croon 10y agoHey, I'm still on Windows desktop after having tried Linux desktop more times than I can count. But to claim that bash (or most other shells) are only preferable to cmd and powershell if you're a linux zealot is what is truly laughable. If you have ever worked with both there would be no question.
- oblio 10y agoI have worked with both and I would not claim that bash is superior to Powershell. I wouldn't even claim that my favorite shell, zsh, which is mostly better than bash, is superior to Powershell. They're different approaches and the only real benefit of bash is that it's super entrenched and extremely widely supported. With the same level of support Powershell would run circles around it. But since we're comparing things in the real world, Powershell is roughly equivalent to bash for most tasks. Better for some, worse for others.
- croon 10y ago> They're different approaches and the only real benefit of bash is that it's super entrenched and extremely widely supported. With the same level of support Powershell would run circles around it. I'm not sure what you mean with this. If you're referring to feature set and robustness with typing in scripting, I might agree with you. I have however a much tougher time agreeing if you also think that powershell could come even close to bash/zsh when working from the shell, in both speed of use (and as you said) support.
- oblio 10y ago> I have however a much tougher time agreeing if you also think that powershell could come even close to bash/zsh when working from the shell, in both speed of use (and as you said) support. At the end of the day, both bash/zsh are "dumb" shells, they don't have the introspection capabilities Powershell has regarding commands they execute. That's both a benefit (they're flexible and you can throw anything at them) but also a disadvantage (they can't really help you much out of the box when you want to run a command; they are only able to help you regarding things they find out from the kernel, such as files, but not arbitrary info from the commands themselves). The reasons that bash/zsh are faster and better supported boil down to history: tens of years of production usage by millions of people. As a result there's this cottage industry of tips and tricks, autocompletion scripts, etc. that makes bash and zsh usable. I'm willing to bet that with a similar amount of man-hours poured into its ecosystem Powershell would beat both of them. But as I said, we live in the real world and both bash/zsh are faster and a bit more robust than Powershell.
- innocenat 10y agoPersonally I want to use PowerShell. The show-stopper for me is that I cannot set default encoding for output redirection (>) to ascii/utf-8. This is so important for things like Google Code Jam, etc.
- ygra 10y agoI agree it's annoying¹, but I wouldn't call it a show-stopper. I have resorted to Out-File -Encoding <foo> wherever I need file output. _________________ ¹ The redirection syntax cannot easily accommodate an encoding, so in general you cannot really use it everywhere anyway. I often need to use the system's legacy codepage instead of Unicode, so UTF-8 by default would be just as useless there. GCJ, however, could just accept text in any common encoding instead of insisting on ASCII. Detecting UTF-16 isn't hard, even though common Unix tools tend to treat it as arbitrary binary data instead of text. Generally I'd say > is a convenience feature more than an actually useful construct, at least in a shell like PowerShell. On Unix-likes > simply dumps bytes since that's what the shell is built around. For PowerShell you could just as well say you'd dump CLIXML instead, since the shell works with objects. Since you have a few valid options you could either try to shoehorn them into the syntax, either with various funny characters Get-Data > data-as-utf8.txt Get-Data >@ data-as-clixml.xml Get-Data >% data-as-utf16.txt ... or add another expression somewhere Get-Data > data-as-utf8.txt,[Text.Encoding]::Utf8 all of which are options I'd say don't really fit into PowerShell, nor should they be entertained. Does it really matter whether the last part of a pipeline is a redirection operator or just a terminating command that writes the data to a file? Conceptually I'd say having the pipeline end in a pipeline element instead of something entirely else is preferable since it reduces the number of distinct concepts.
- JeffreySnover 10y agoHere is how you do that: $PSDefaultParameterValues["Out-File:Encoding"]="utf8" Jeffrey Snover [MSFT]
- cryptos 10y agoIt would be nice, if they would improve the terminal window a bit with tabs and the like (like Gnome Terminal for example).
- _pmf_ 10y agoIt's already slightly better in Win10 (in case you have not tried it yet).
- TorKlingberg 10y agoMeanwhile, Gnome Terminal has been taking away the tabs...
- tonyplee 10y agoDid they, why? I have switch to xfce4-terminal for a while in all my system....
- zlynx 10y agoThey didn't take away terminal tabs.
- poizan42 10y agoPsst, try pressing ctrl+alt+t in a terminal window
- alfalfasprout 10y agoYeah, I haven't liked many of the changes in Gnome over the past few years. Terminator as a terminal emulator has been rock solid though. Highly recommend it.
- mhd 10y agoBy the way, where does the capitalized kebab case come from? Prior art or just Microsofts general hankering for capitalization (e.g. C#s Class.DoSomething() vs Java's Class.doSomething())?
- Aaronepower 10y agoWhat you're thinking of is PascalCase https://en.m.wikipedia.org/wiki/PascalCase https://en.m.wikipedia.org/wiki/PascalCase
- pritambaral 10y agoYour parent probably meant Kebab as in the dash (skewer-stick) between words.
- 794CD01 10y agoWikipedia calls it Train-Case but doesn't provide a source. https://en.wikipedia.org/wiki/Letter_case#Special_case_styles https://en.wikipedia.org/wiki/Letter_case#Special_case_style...
- int_19h 10y agoNote that it's not quite "kebab case". The dash only separates the initial verb from the object, but the rest of it is regular PascalCase. So Get-ChildItem, not Get-Child-Item. PascalCase is well-established in the Microsoft developer ecosystem. It goes at least all the way back to Win16 and Windows 1.0 (it using the Pascal calling convention might have something to do with it, perhaps). More importantly, it is used uniformly in .NET, and PowerShell builds on top of .NET, and deals with .NET objects directly, which have properties like e.g. `FullName`. So it makes sense for consistency.
- mikerg87 10y agoWeird. I have 14971 installed and when I type CMD in the "ask me anything" box or in the alt-r box I get good old CMD shell. Is this a config thing ?
- Already__Taken 10y agoThey're not removing cmd the console host. If you shift-right-click a folder the context item is powershell now instead of command prompt.
- sp332 10y agoSame, if I type "cmd" into the start menu, I get plain old cmd.
- l3m0ndr0p 10y agoOMG - PowerShell is better, but still, it's slow and verbose. I mean, extremely verbose. They should have used C# as the powershell command language, it looks almost the same, or even F#.
- gigatexal 10y agoI welcome this 100%.
- marianov 10y agoHow does PS compare to installing cygwyn and using bash ? (from a Linux user perspective) does it support grep, find, ls, PS, pipes, etc?
- steve-howard 10y agoWindows 10 actually has some fancy linux emulation stuff ( https://insights.ubuntu.com/2016/03/30/ubuntu-on-windows-the-ubuntu-userspace-for-windows-developers/ https://insights.ubuntu.com/2016/03/30/ubuntu-on-windows-the... ). Personally I wanted to like PowerShell but its syntax and semantics were infuriatingly confusing.
- new_hackers 10y agobetter? with PS you pipe objects. The pipeline is very much the way to move data between cmdlets. each of the linux commands you listed has an equivalent PS cmdlet.
- nailer 10y ago> Starting with Windows 10 build 14971, Microsoft is trying to make PowerShell the main command shell in the operating system. > As a result, PowerShell officially replaces the Command Prompt in the Win + X menu, so when you right-click the Start menu, you’ll only be allowed to launch the more powerful app. This is an older change - I have this behavior in 10.0.14393.0 (ie, current stable). cmd launching posh is new though.
- ygra 10y agoThere's an option in the Taskbar settings: »Replace Command Prompt with Windows PowerShell in the menu when I right-click the start button or press Windows key+X«. I suspect the default value for that setting has been false, so far.
- nailer 10y agoI have that here in stable. I suspect you're right and changing the default might be what they mean (I think I already changed it because cmd is gross).
- ashmud 10y agoI know we have machines with lots of RAM now, but at 90-100MB (PS) vs 4MB (CMD) [1] RAM usage per instance (not counting the conhost instance that also spawns), I think I would still want CMD around. [1] Quick check done on my Win7x64 laptop.
- Klathmon 10y agoDoes that really affect you in any way? (And I'm really asking, not trying to be snarky, I've got 64gb on my main dev machine so I really don't know...) I can't imagine any scenario in my actual usage where I'll have 4mb (plus whatever is needed to actually do the work) but not 100mb (plus whatever is needed to actually do the work). Also, on my machine (windows 10 stable branch) each PS window takes up about 20mb (at least the task manager is telling me that, I didn't dive any deeper)
- ashmud 10y agoMy work machine is not nearly that beefy. :| I do often have 8-10 cmd windows open. According to task manager on my machine, each PS instance on start is 90-100MB. I didn't dig deeper to see if that RAM usage would shrink over time.
- ergot 10y agoPowershell is very insecure and is heavily abused by potential attackers as it's more flexible than CMD.exe. Of course, arguing about CMD.exe vs PS.exe is pointless, but it still needs to be argued. There has been a recent spate of talks in Blackhat conf. and other confs, about the versatility of PS.exe, how it is used to perform persistence in comparably little characters, or lines of script than CMD.exe Some of my Win10 deployments even contain a script which silently disables PS.exe in the installation, and removes every reference to that executable in the registry. There are a few cases where I caught PS.exe re-spawning itself when a Win10 update arrives, so a PS-free deployment is hard to enforce.
- gecko 10y agoI'm really confused here. What attack vectors apply to PowerShell, but not to a situation where I can invoke cmd.exe? I can tell PowerShell to only run signed scripts, and specify what signatures to honor, which is more than I can do with either cmd.exe or WSH. You're citing compactness of scripts, but a straight-up binary would be more compact still. I think I'm missing something pretty basic here.
- ergot 10y ago> I think I'm missing something pretty basic here I'm referring to something like Powersploit https://github.com/PowerShellMafia/PowerSploit/ https://github.com/PowerShellMafia/PowerSploit/ Which is a post exploitation tool. Assuming you have a payload in Windows ready to execute, one typically wants to leverage tools already in Windows itself, like Powershell, which can make rootkits and other payloads have a lot less footprint, and make them difficult to spot using heuristics. Most crap payloads are actually easy to spot because their payload is massive. Essentially my point is that you don't want to make it easy for attackers. For context, one would not want Powershell installed on 1000 Windows 10 installations. I happen to get paid good money for deploying Win10 kiosks in different offices in my area and Powershell is one of many tools I routinely remove from Windows to decrease the attack surface in Win
- UnoriginalGuy 10y agoAnything VBS can do, Powershell can do ("everything" that a running user has the security for). Number of characters isn't relevant to scenarios where you're running PS/VBS/CMD on a local machine. PS - Your "PS breaker" machine configuration is going to cause problems. Several of Microsoft's installers already run PS scripts behind the scenes. Plus you're doing it for absolutely no technical reason (just ignorant fear).
- tonyplee 10y agoWhat happens if someone have batch files for some work flow routines? Have to re-write all of them?
- UnoriginalGuy 10y agoNothing. Bat is a filetype, that file type is bound to executive in CMD's context. You can even execute it from PS and have it run the Bat perfectly normally (using CMD). Ditto with VBS. You can execute VBS files from any context on Windows (e.g. double click, PS, CMD, etc) and they'll always use the cscript engine.
- WayneBro 10y agoWindows fan here. I hate PowerShell and I'd much rather have Bash built into Windows. Things I hate about PowerShell: - You can't even run your own scripts without performing the Set-ExecutionPolicy ceremony first or signing your scripts. - It's way too verbose. - It's a strange bird that next to nobody uses, so there's zero motivation to learn it. - It's not "old reliable". You can't depend on it working due to the first point and also due to the fact that they're still working on it and even in 2016 they broke some PowerShell stuff with updates that needed to be uninstalled (KB3176934).
- UK-AL 10y agoLiterally every windows admin uses it. It's the official commandline interface for microsoft software. Every piece of microsoft software must provide a ps interface. It's an engineering directive.
- jordache 10y ago"admin" This would be a good move if it was on Windows Server.
- treebeard901 10y agoIt is strange to claim no one really uses powershell. It is widely used in the Windows world. The main complaint I see about powershell is that it isn't bash. The object pipeline in powershell can be so much more powerful than parsing text between commands. After all, that's why we have data types instead of storing everything in strings.
- WayneBro 10y agoIt's not widely used in the Windows world from what I can see. Walk into any office and ask an IT guy to run "ipconfig". They'll open up cmd.exe without even thinking about it. I read a lot of programming tutorials. Nobody ever reference PowerShell in them. They always instruct people to open cmd. Do you have any evidence to the contrary?
- Stratoscope 10y ago> Microsoft is expected to get rid of [Command Prompt] completely at some point in the future. This is extremely unlikely to ever happen. As long as people have .cmd and .bat files they need to run, cmd.exe will still be around. They're not going to just remove it and break all those scripts.
- JeffreySnover 10y agoThat is right. CMD.exe will be around to support script execution for a long long time. Jeffrey Snover [MSFT]
- Bedon292 10y agoI think this is probably a step in the right direction, but it still only has 16 colors. When are we going to get a command prompt with at least 256 colors on Windows? There are already a bunch of linux consoles out there with true color, but nothing for Windows. Am I crazy for caring about this?
- aq3cn 10y agoThat's not all in latest build 14971. Cortana supports to do list now Dial support for map app Bringing 3D to Everyone via the Paint 3D Preview app (RIP paint.exe, I am going to use picpick or paint.net from now on) Read EPUB books in Microsoft Edge Improved Typing Experience with Japanese and Chinese Input Method Editors New Get Office hub for Windows Insiders source: http://winaero.com/blog/microsoft-is-killing-the-classic-paint-app-in-windows-10-creators-update/ http://winaero.com/blog/microsoft-is-killing-the-classic-pai... http://winaero.com/blog/microsoft-releases-new-get-office-hub-for-windows-insiders/ http://winaero.com/blog/microsoft-releases-new-get-office-hu... http://winaero.com/blog/edge-gets-epub-support-in-windows-10-creators-update/ http://winaero.com/blog/edge-gets-epub-support-in-windows-10... https://www.neowin.net/news/cortana-will-now-keep-track-of-your-to-do-lists https://www.neowin.net/news/cortana-will-now-keep-track-of-y... https://www.neowin.net/news/microsoft-adds-support-for-surface-dial-new-touch-features-inside-of-maps https://www.neowin.net/news/microsoft-adds-support-for-surfa... https://www.neowin.net/news/windows-10-build-14971-for-pcs-now-available-in-the-fast-ring---here039s-what039s-new https://www.neowin.net/news/windows-10-build-14971-for-pcs-n... https://www.neowin.net/news/here039s-what039s-fixed-improved-and-still-broken-in-windows-10-for-pcs-build-14971 https://www.neowin.net/news/here039s-what039s-fixed-improved...
- rhabarba 10y agoI use ConEmu with PyCmd but I surely see why Powershell is an interesting alternative. I'm just too lazy to get used to its command syntax.
- vic-traill 10y agoPS is pretty robust, but it's a bit verbose, to say the least. As noted elsewhere, command processors internals like 'dir' and 'copy' are supported, but aliased to something else. In the case of dir it's aliased to Get-ChildItem, and copy to Copy-Item. The latter breaks my favourite quick file create method: C:\temp>copy con example.bat [return] commands go here^Z 1 file(s) copied. I had a quick look at Copy-Item and there is no obvious way to use it to the same effect that I can see. [edit: added the [return] to make it more obvious]
- ChuckMcM 10y agoI like the signalling that perhaps Microsoft is taking the command line shells seriously for their users for the first time in a long time.
- jongalloway2 10y agoI'm pretty sure the Softpedia article is incorrect in saying that "cmd" is now aliased to powershell. I installed the update, and running cmd from search bar (win cmd enter) and from run dialog (win+r cmd enter) both launch cmd.exe. The release announcement post says "Typing “cmd” (or “powershell”) in File Explorer’s address bar will remain a quick way to launch the command shell at that location." I honestly kind of wish it was aliases - I regularly launch a cmd window due to decades of muscle memory, then remember I really probably wanted powershell.
- nmc 10y agoOfficial announcement: https://blogs.windows.com/windowsexperience/2016/11/17/announcing-windows-10-insider-preview-build-14971-for-pc/ https://blogs.windows.com/windowsexperience/2016/11/17/annou...
- mgregory22 10y agoWill Far Manager still work?
- serge2k 10y ago> as it replaces the super-popular Command Prompt heh. heh heh heh. hahahahahahahahahahahahahahaha
- Animats 10y agoIs it Unicode by default now?
- ZeroClickOk 10y agoSo many surprise and complains... Simply change what you want, PowerShell is cross-platform and opensource: https://github.com/PowerShell/PowerShell https://github.com/PowerShell/PowerShell
- oakwhiz 10y agoI hope the old CMD.exe is still available somewhere.
- EastSmith 10y agoDid they finally add persistent history oit of the box? Peristent = close the terminal then open it and the last commands are available. And yes, I know you can hack it to be persistent.