Microsoft removes some policies from Windows 10 Pro

You have chilled any further interest I have in being part of the discussion as to what could happen if MS continues on the path they are on.

It's almost like bait and switch what they're doing. I bought Pro specifically for gpedit.msc.

altae said:

I'm using it every day and the more MS bothers it's customers with stupid moves like the upgrade trickery (well, for the last 20 years the x stood for "close" but as of now it stands for "accept") the more I'm starting to like it.

For starters, you're mischaracterizing the situation with the upgrade. The dialog was confusing, but the X did not "stand for accept". The dialog was informing you that the upgrade had already been scheduled (not asking you if you wanted to schedule it), the dialog was just a notification of it, so closing the dialog did nothing. It wasn't accept, it was "close the notification window". I'm not arguing that the dialog wasn't confusing, as it was. But it wasn't any "trickery" nor was it violating any Windows guidelines. Most people just misunderstood what it was telling them.

Second, it doesn't matter anyways. The free upgrade offer is over, and the entire issue is now moot. You won't be seeing any more free upgrades, so-call "forced" or not.

Finally, there really aren't any alternatives for most people. Mac's are too expensive, and Linux is too confusing. And that assuming they aren't locked into Windows because they need to run specific apps. For instance, many companies use VPN software that is windows specific. So if you need to work from home, you need windows.

Culbrelai said:

It's almost like bait and switch what they're doing. I bought Pro specifically for gpedit.msc.

You seem to be confused. That's a silly reason to buy pro, since everything you can do with gpedit is doable by registry entries. Regardless, gpedit is still present. It's just a few handful of entries that don't apply to pro, just like a bunch of entries don't apply to home. And a bunch only apply to server editions. This is nothing new.

W2BLC said:

You have chilled any further interest I have in being part of the discussion as to what could happen if MS continues on the path they are on.

There's really not much to discuss. Microsoft is on the path they're on, and nothing you or I or anyone else can say will change that. It's not "if", it's what is happening. So arguing as if there is any choice in the matter is silly.

You seem to be confused. That's a silly reason to buy pro, since everything you can do with gpedit is doable by registry entries. Regardless, gpedit is still present. It's just a few handful of entries that don't apply to pro, just like a bunch of entries don't apply to home. And a bunch only apply to server editions. This is nothing new.

What kind of precedent does this set though? I have always liked Windows for it's tweakability, it's huge library of programs (literally how many applications have been made for windows over the years? 100 million? Take that Apple App Store)

I find any chipping away at user modability to be quite insulting. Lock out gpedit.msc features on Home of course but Pro? Really? Force security features down our throats that we neither want/need/asked for? No update controls? Sigh.

Luckily, like with the Windows 8 start menu debacle, someone will be there to save the day and make a 3rd party program. <3 Classic Shell

Mystere said:

You seem to be confused. That's a silly reason to buy pro, since everything you can do with gpedit is doable by registry entries. ....

You can probably make that same statement about every feature that Pro has. It has more function than Home, and every one of those functions is probably not reason to buy Pro. But we that bought Pro bought it for its additional function. Gpedit is one of those functions.

In addition, I trust gpedit a lot more than I trust my use of Regedit (or equivalent 3rd party products). I also figure that an option that can be changed via gpedit is recognized by MS as a customizable option. I have no such warm, fuzzy feeling about registry entries. I have no idea what registry values have to be simultaneously changed, for example, to leave Windows healthy.

I know that gpedit will continue to exist. I know that the registry entries will probably continue to exist for those options removed from gpedit. And I know that people on this forum will figure out and publish tips for making registry changes to accomplish what MS has removed from gpedit. But I don't like MS forcing me to jump through hoops to accomplish (what had been) simple customization tasks.

At least Microsoft documents the Group Policy settings for various Windows versions in the form of Excel (.xlsx) spreadsheets for reference, available for download, at:

Download Group Policy Settings Reference for Windows and Windows Server from Official Microsoft Download Center

- with further information and documentation available at:

Group Policy