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

Anonymous

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.

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

Anonymous

2022-02-20T02:09:27+00:00

As a result of running chkdsk c: /f the new Task Manager is back. 🤣

Hi fg,

Interesting indeed.

I don't want the new TM but just to confirm your findings, I ran chkdsk c: /f but did not get it back.
Was this answer helpful?

0 comments No comments
Anonymous

2022-02-20T01:51:04+00:00

Hi Sibro,

This is interesting!

They still have the old bug that causes all the experimental feature configuration to be deleted when running chkdsk c: /f , i t was fixed on some previous Dev build, but it is back with 22557. 🤐

I just tried to run chkdsk c: /f

Replied yes to run on next restart.

As I suspected after the scan is done, it comes up with all the feature configurations wiped out including the ones that disabled the new task manager. It looks like the new Task Manager is enabled by default, so it works fine without any of the feature configurations.

The problem with this is that if there is any other new feature that they are testing and enabled with a feature configuration it is gone too till the reload all that stuff from the server.

This problem has been reported several months ago when they were testing other experimental features, but apparently, they don't care fixing the problem. 😵‍💫

As a result of running chkdsk c: /f the new Task Manager is back. 🤣

Time for another FBH:

https://aka.ms/AAfrz9m
Was this answer helpful?

0 comments No comments
Anonymous

2022-02-19T20:35:20+00:00

Today they reverted back to the old Task Manager again on one desktop

Hi fg,

They reverted mine too, the one from yesterday's clean install, the only one I have 🤣

Weird that they still did not touch my older desktop, it still has the new Task Manager as it was the 1st day, when I updated it through W.U.

Maybe they are enabling only for users that they know will give positive feedbacks.

(Job Security project!) 🙃
Was this answer helpful?

0 comments No comments
Anonymous

2022-02-19T20:27:11+00:00

Today they reverted back to the old Task Manager again on one desktop

Hi fg,

They reverted mine too, the one from yesterday's clean install, the only one I have 🤣
Was this answer helpful?

0 comments No comments
Anonymous

2022-02-19T18:33:43+00:00

Today they reverted back to the old Task Manager again on one desktop, while the other one still has the new Task Manager.
Was this answer helpful?

0 comments No comments