Microsoft is changing Win10’s default command processor to PowerShell. Here’s how to ensure batch files and other legacy operations still work.
Plus: Should you uninstall old apps before installing new versions; also, a question about questions and an end-of-year best-wishes to all!
Win10 change stops classic batch files cold
Writing from India, Windows Secrets reader Chandrasekharan Kunnath reports new trouble with old batch files.
- “Batch files executed correctly on my Windows 10 system — until yesterday. Now they won’t work. Can you help me with with this problem?”
A batch file is really nothing more than a plain text file with a .bat extension. The file contains a list (aka “batch”) of system commands, each on a separate line. In Windows 10, cmd.exe executes these commands in serial fashion, just as if you’d manually typed them in, one by one, at a command prompt. (For more information, see the TechNet article, “Using batch files,” and the Wikipedia page, “Batch file.”)
Cmd.exe is also the same subsystem that creates and runs the DOS-like command windows, opened with Command Prompt (via Win + X or right-click Start) or launched by entering “cmd” or “command” in the Cortana search box.
But Microsoft is making a change to the Command option in upcoming Win10 versions. (The change is already in Win10 Preview Build 14971, which I’m betting Chandrasekharan is running.)