[Resolved in Build 22567] New Task Manager reverting back to the old style with Build 22557.1, randomly on different machines.

Anonymous
2022-02-18T16:00:07+00:00

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.

0 comments

103 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. 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

  2. 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

  3. Anonymous
    2022-02-21T21:31:55+00:00

    At this point I don't have any idea why it behaves differently on the desktop versus the laptop clean install of the same Build 22557?

    Hi fg,

    Would be nice to hear something from them, anything...

    As per our previous discussion, vivetool does not remove the new TM from a clean install,

    do you you know of any other way? I want the old one back.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-02-21T02:38:03+00:00

    Hi Sibro,

    Just for further verification I made a clean install of 22557.1 on the Dell XPS 8930 desktop and checked the behavior of "chkdsk C: /f" right after that.

    I was surprised to see that in this case, even after the clean install of 22557 it still wiped out all the hidden feature configurations.

    At this point I don't have any idea why it behaves differently on the desktop versus the laptop clean install of the same Build 22557?

    I'll just add another comment to the FBH report, I hope MS comes back with some clarification.

    More and more inconsistency! 🤐

    https://aka.ms/AAfrz9m

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-02-20T19:58:12+00:00

    Why is this machine treated differently? 😎

    You are asking me? 🤣

    Put your detective skills to work and find out 😜, just kidding!

    I seriously doubt they would tell us that.

    I'm more interested to find out why chkdsk behaves differently when it wipes out the hidden feature configurations in one case, but not the other.

    It is an old bug that just resurfaced. 😒

    Was this answer helpful?

    0 comments