[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-20T09:36:12+00:00

    @BriceSor,

    About "weird or what" you may take a look at some other tests results on my post just above. 🤣

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-02-20T08:26:58+00:00

    Hi Sibro,

    Now the puzzle is getting more complicated.

    After a clean install of 22557 on the MSI Laptop I checked the feature configurations which were present as expected, except the 2 that disable the new T.M.

    I then did a

    chkdsk C: /f

    which ran the scan on restart as expected but, in this case, it did not delete any of the existing feature configurations which remained exactly as they were before the scan.

    I repeated the chkdsk 3 times and nothing was deleted.

    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? 🤷‍♂️🤷‍♂️

    So, I restored the same laptop with an image that was previously updated from 22543 to 22557 and repeated the same experiment with chkdsk C: /f

    This time it wiped out all the feature configurations as it did on the desktop. This confirms that the different behavior is due to the previous builds updated to 22577 versus the clean install of 22577, rather than a specific machine configuration.

    Somebody at MS should explain what they do different on the clean install that fixes this bug.

    At least I could verify the same results as yours. Half mystery solved! 👍 I hate the inconsistent results.

    Thanks.

    I hope they can fix the problem also on systems updated from previous Builds.

    Most users don't do clean installs, they update from previous Builds. 🤷‍♂️

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-02-20T07:34:22+00:00

    I'm sorry but I need to go to bed now.

    During those hours I was offline I had too much to drink at a dinner with friends.

    Talk to you tomorrow, good night!

    Goood night

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-02-20T07:28:21+00:00

    I'm sorry but I need to go to bed now.

    During those hours I was offline I had too much to drink at a dinner with friends.

    Talk to you tomorrow, good night!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-02-20T07:24:33+00:00

    Do you have all the info you need or is there anything else you need from me?

    Still a question of why chkdsk is not cleaning up the configs on your laptop.

    I'm just trying a clean install on a laptop here to see how it behaves, I'm almost done.

    B.T.W.

    Clean install still let me use local account, no MSA.

    Was this answer helpful?

    0 comments