Startup Impact  

The Startup impact works just fine in the Development Insider channel, but as you may be aware is broken in RTM, RP, and Beta. I found a simple 1 byte fix in the registry you may want to try. It brings back the Task Manager Startup Tab Impact functionality. I ran it for several weeks on RTM without anything breaking or stopping, then a Cumulative set my .reg change back, so just did it again. This is not a permanent "Fix". The only thing you will notice is WINVER will display 20H2 with 19041, a bit bizzare looking but appears to be only cosmetic.

You will need to edit permissions on this key to allow modification or use Power Run like I do, which runs REGEDIT in TrustedInstaller mode. PowerRun v1.4 (Run with highest privileges)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\EditionVersion

Then change 1 value in 1 key.

only changed 4a62 to 4a61 (19042 to 19041)

"EditionBuildNumber"=dword:00004a61

Close REGEDIT and reboot.

Done.

All caveats reserved.....

Thanks f14tomcat. After applying that fix, when will measurements be visible- and is it necessary to restart/log off?

As ever, best to export the original key by way of backup.

Power Run: from
PowerRun v1.4 (Run with highest privileges)

dalchina said:

Thanks f14tomcat. After applying that fix, when will measurements be visible- and is it necessary to restart/log off?

As ever, best to export the original key by way of backup.

Power Run: from
PowerRun v1.4 (Run with highest privileges)

Yes, Reboot.

Also, the xml files will be in this directory. They do not appear instantly after restart, maybe a minute or two later after time for processing. These files, most current one, are used to calculate Startup Impact.

for reference, these are the Startup Impact columns. If you do not currently show them, right-click any header column and add them.





Mine is currently empty because it contained very old useless data.

Thanks- I'm experiencing the impact now..

dalchina said:

Thanks- I'm experiencing the impact now..

f14tomcat said:

Yes, Reboot.

Also, the xml files will be in this directory. They do not appear instantly after restart, maybe a minute or two later after time for processing. These files, most current one, are used to calculate Startup Impact.

for reference, these are the Startup Impact columns. If you do not currently show them, right-click any header column and add them.





Mine is currently empty because it contained very old useless data.

Worked a treat thank you 👍

Dick,
Does the Startup fix get undone every CU or have you been running it for a duration where you've only installed one CU with the fix in place?

I still plan to try it, just wondering

EDIT: Did the mod and unsurprisingly it's working as advertised

So am I running 20H2 or it it 2004 in a 20H2 mask? I'll have to go find out a change made between 2004 and 20H2 that I can check for, I suppose.

Somewhat disconcertingly, although I'm on 20H2, I got this update notification for 2004 this morning:


Wonder if that's related to the change for this fix?

Granted this one's repeatedly updated, but it's something to do with preparing for an upgrade, I think.

dalchina said:

Somewhat disconcertingly, although I'm on 20H2, I got this update notification for 2004 this morning:


Wonder if that's related to the change for this fix?

Granted this one's repeatedly updated, but it's something to do with preparing for an upgrade, I think.

Just checked and no update available. KB4023057 installed was 13th Feb.

dalchina said:

Somewhat disconcertingly, although I'm on 20H2, I got this update notification for 2004 this morning:


Wonder if that's related to the change for this fix?

Granted this one's repeatedly updated, but it's something to do with preparing for an upgrade, I think.

Don't get that update. I did do an in-place for cleanup purposes on 4/01, and have no record of it ever being installed. I always do in-place with check for updates, so it may have been in the bundle.