Do you want me to try a VM to see what happens?
[Resolved in Build 22567] New Task Manager reverting back to the old style with Build 22557.1, randomly on different machines.
After updating to Build 22557.1 on 2/16/2022 the new style Task Manager showed up and worked as advertise in the blog except for a minor bug with the Title of the tabs defaulting to Processes regardless of the tab selected to open as default in settings.
A day later on 2/17/2022 the new Task Manager started to revert to the old style on some machines randomly.
Other machines still have the new style Task Manager.
It appears to be another typical A/B testing done by MS without any warning to the users.
On one machine it reverted back again on 2/18/2022 after I restored it to the new style the day before.
I have no problem participating in A/B testing, but I'd like MS to notify when they change those experimental features so that the users are not left guessing on what is happening.
This comment is in the Blog:
[We are beginning to roll this change out, so it isn’t available to all Insiders just yet as we plan to monitor feedback and see how it lands before pushing it out to everyone.]
FEEDBACK: Please file feedback in Feedback Hub (WIN + F) under Desktop Environment > Task Manager.
Windows Insider program | Windows Insider preview | Desktop environment and Start menu
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
103 answers
Sort by: Oldest
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2022-02-20T06:00:14+00:00 -
Anonymous
2022-02-20T06:07:52+00:00 Do you want me to try a VM to see what happens?
BryceSor earlier said he already got the same behavior as mine in 3 machines out of 4 except for the SP4.
Sounds more like a policy setting difference.
There is one in the registry called AllowExperimentation, maybe we can compare the settings?