Finally, the death of CMD!

February 2nd, 2015 by and tagged , ,

Well, OK, it’s still there in Windows 10 But finally, completely, I no longer need it for ANYTHING! The final piece that I still used is now available in PowerShell v5. The latest publicly available Preview Build of Windows 10 Technical Preview (build 9926), includes updates to New-Item to support Junctions and Hard Links. Finally!


There’s no direct help available for it yet (I checked and downloaded the very latest), but a little poking around produced:

PS> New-Item -Type HardLink -Path 2ndTest.txt -Value Test.txt

I can edit 2ndTest.txt and the changes appear in Test.txt, and I can delete Test.txt and 2ndTest.txt is still there and editable. Interestingly, I do NOT need to run this as an administrator, assuming I have permissions in the folder where I’m creating the second (or third or 15th file). And, as expected, this can’t cross drive boundaries.


This build also includes support for directory Junctions, (-Type Junction) so between these two, I think we finally have all we need to kiss goodbye all further use of cmd.exe. (I really hate having to use cmd c/ from my PowerShell to get something done. Really. It’s so DOS.)


My thanks to the PowerShell team who took my challenge and mantra of Death To CMD to heart and have finally made Windows PowerShell the tool I can use for everything.

(Note: Currently the most current build available for download separately is the November build which doesn’t have these two New-Item features, so the only way to get them right now is in the latest Windows 10 build. But that’s likely to change soon.)


ETA: The February WMF 5.0 build is available from Windows Download Centre. This includes support for Windows Server 2012, Windows Server 2012 R2, and Windows 8.1 Pro and Enterprise. And yes, the changes to New-Item are in there. :)


Oh, and while we’re at it – there’s all sorts of other goodies in PowerShell v5, including OneGet, a great way to get new modules for your PowerShell. Check it out.

Posted in Network Administration, PowerShell, Windows Server | 2 Comments »

2 Responses to “Finally, the death of CMD!”

  1.   Chris Knight Says:

    The advantage of CMD is it’s available on all systems, has a mature and stable programming interface, and you don’t need to install a specific version depending on which OS version you’re running or even worse what server applications are installed.
    I’d love to roll out the same version of PowerShell to every Windows instance under my control. Sadly Microsoft don’t make this possible.

    •   Charlie Russel Says:

      Yes, CMD is there. No, I don’t care. Some form of Windows PowerShell is available on every machine I support, and when WMF5.0 releases, a version that closes the last few gaps in coverage will be available for every version of Server and Windows client that I have to live with. As for upgrading those machines to WMF5.0? Not an issue, except for my ancient SBS box.