That's something I've noticed over the years. More and more of Windows debugging and configuration is happening on the (various) command line terminals. You're even starting to see it with official Microsoft installers.
It has tiers these days. You might need the new settings thingy (is it still called a “charm”? I hope not) or the control panel or MSC (which you might need to start from Win+R or the command line) or actually the command line. There seems to be no a priori way to figure out where a seething is.
It's where developers are learning. Most of my learning was done on a (Linux) command line. Making things usable on the command line makes sense to people like me.
