Control panel is still not migrated over to settings after 12 years nor you can open two settings apps.
I wish they'd migrate back to the old Control Panel...
Error messages in modern apps are just the worst
...as the new one is a "modern app" and about as horrible as they come.
From an elevated Powershell prompt:
Get-AppxProvisionedPackage -Online | Where-Object { $_.PackageName -like 'Microsoft.WindowsNotepad*' } | Remove-AppxProvisionedPackage -Online
One bit of cruft with this - I downloaded an alternative app that is simply notepad.exe and put it in my path in the first folder in the path.
I could not create a file association to any files to it - Explorer would throw an error about Store app. Even after uninstalling it, a notepad.exe still remains and supercedes my path which is a stub to launch the Microsoft Store.
This is the type of slop that needs desperately fixed but I doubt ever will.
They have a bunch of replacements, all of which are slow as molasses and not feature complete.
1. Server Manager.
2. Windows Admin Centre.
3. Settings App (same as desktop).
4. PowerShell
5. DSC
6. Azure Arc
There's also Active Directory Administrative Center which never replaced dsa.msc for me or anyone I've ever worked with.
Similarly, there's like half a dozen performance monitor tools for Windows Server, and they're all terrible and are missing critical features.
It also takes a solid two seconds to launch even on a high-end PC with a fast SSD. It takes much longer on a small VM with overpriced cloud remote storage.
1. deprecated lol
2. i think it can't be run on things like AD, so for very small companies this is annoying
3. ... that's not really an admin app?
4. sure, but then i might as well switch to linux if i have to stick to cli (and i did)
5. last time i checked there were two versions, incompatible with one another, not great alternative to ansible
6. if you have hybrid and are in azure already, maybe? haven't used
I mean it's not like there are not 5 alternatives in azure/intune for every thing as well that are half baked. And 365 and azure is worse with terrible migration guides, ms graph with a combination of commands and json inputs and defaults from 2016.
It's really time for microsoft to fully commit to one thing, make it good, finish it and deprecate everything else.
It launches by default on new installs of Windows Server 2025!
> 2. i think it can't be run on things like AD, so for very small companies this is annoying
In "Preview", which is a sad state of affairs: https://learn.microsoft.com/en-us/windows-server/manage/wind...
> 3. ... that's not really an admin app?
I was just listing stuff that generally replaced the old MMC consoles. Things like regional options can be set through the Admin app, and is weirdly difficult with other mechanisms even on Windows Server. Some critical aspects are still MMC-only or require half a page of PowerShell scripts.
> 4. sure, but then i might as well switch to linux if i have to stick to cli (and i did)
Ironically, you're missing out on PowerShell, which is more UNIX than UNIX, and blows every legacy shell on Linux out of the water.
> 5. last time i checked there were two versions, incompatible with one another, not great alternative to ansible
There are three now, all incompatible and incomplete: https://dsccommunity.org/blog/what-is-microsoft-dscv3/
> 6. if you have hybrid and are in azure already, maybe? haven't used [Azure Arc]
It's supposed to replace Group Policy, Windows Update, and bits and pieces of SCCM and SCOM.
It is incredibly, hilariously bad at all of those things.
It's a level of failure that simply boggles the mind, and I can only surmise that it was developed by a small army of junior outsourced Indian developers that had never seen any of the tools they were replacing and did everything "to the letter of the spec".