[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. Anonymous
    2022-02-24T20:48:48+00:00

    Still the old Task Manager on Build 22563.1.

    Had to pin to Taskbar after using Ctrll + Shift + Esc to open because Win + X is broken.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-02-23T06:25:44+00:00

    You'd have a better chance addressing your post directly to Jason or open a new thread @Jason [MSFT]

    Already asked a question earlier, we'll see what he says.

    oops! sorry I missed it. 🤐

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-02-23T06:17:59+00:00

    You'd have a better chance addressing your post directly to Jason or open a new thread @Jason [MSFT]

    Already asked a question earlier, we'll see what he says.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-02-23T05:42:08+00:00

    I'd really like to have a clarification from MS, but I'm afraid I'll never get one. 🤐

    Maybe they have 2 different places for storing or saving these configs, but why are they still deleted by chkdsk on some cases and not always?

    You'd have a better chance addressing your post directly to Jason or open a new thread @Jason [MSFT]

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-02-23T04:58:17+00:00

    Next test will be to run chkdsk while disconnected from the network to see if those a saved locally or not.

    You don't give up easily, do you?

    Dare I say looking forward to your findings? 🤣

    Looks like it is saving these somewhere locally, because when I did the "chkdsk C: /F" with the network disconnected these 5 configs where still there untouched after the scan was done on reboot,

    The same 5 were originally there after the clean install.

    If I add some other configuration manually on top of the original ones they get wiped out by "chkdsk C: /F" while the original ones are not affected. I'd really like to have a clarification from MS, but I'm afraid I'll never get one. 🤐

    Maybe they have 2 different places for storing or saving these configs, but why are they still deleted by chkdsk on some cases and not always?

    Was this answer helpful?

    0 comments