[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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-02-20T19:48:11+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.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-02-20T19:09:08+00:00

    That is the way they do A/B testing on selected machines.

    VMware and Hyper-v VM are yet another game that apparently are treated differently.

    Good luck getting MS to explain the differences. 😜

    Yeah, I'd like to know why would they consider a VM worthy of A/B testing over a real machine, specially a VM not meeting all the requirements.

    Hi Sibro,

    This is a real machine, (Dell desktop) and never got the 2 disabled config files that we discussed earlier.

    So, the T.M. is still the new one, it never reverted back from the beginning when it was updated to 22557 with W.U. on 2/16/2022. Why is this machine treated differently? 😎

    Image

    Note that my insider machines are all using the same insider account.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-02-20T18:56:59+00:00

    That is the way they do A/B testing on selected machines.

    VMware and Hyper-v VM are yet another game that apparently are treated differently.

    Good luck getting MS to explain the differences. 😜

    Yeah, I'd like to know why would they consider a VM worthy of A/B testing over a real machine, specially a VM not meeting all the requirements.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-02-20T18:46:18+00:00

    That matches what you got on your laptop after the clean install of 22557.

    The question remains, why the different behavior on the Desktop updated from previous build 22543 versus the laptop with the clean install of 22557? 🤷‍♂️🤷‍♂️

    Hi fg,

    Also the question why TM behaves differently on a clean install VM?

    It's not reverting back to the old one automatically and it doesn't have the performance tab bug.

    It is not just VM, I have a desktop that never reverted back to the old T.M. because it never got the added disabled configuration from the server.

    It is still working with the new T.M., never changed from 2/16/2002 to 2/20/2022.

    That is the way they do A/B testing on selected machines.

    VMware and Hyper-v VM are yet another game that apparently are treated differently.

    Good luck getting MS to explain the differences. 😜

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-02-20T18:31:07+00:00

    That matches what you got on your laptop after the clean install of 22557.

    The question remains, why the different behavior on the Desktop updated from previous build 22543 versus the laptop with the clean install of 22557? 🤷‍♂️🤷‍♂️

    Hi fg,

    Also the question why TM behaves differently on a clean install VM?

    It's not reverting back to the old one automatically and it doesn't have the performance tab bug.

    edit: I was wrong about the bug.

    The title it is always Processes not matter which tab you chose to open it with.

    Was this answer helpful?

    0 comments