Insider KB5089417 Windows 11 Insider Beta (25H2) build 26220.8370 - May 8

Thorenzz · May 9, 2026

FrancoDT said:
From everything I've read the CPU burst are so brief that it's not enough to generate heat or cause any wear and tear on the CPU's. They are doing what they were designed for. Course this may be a subject of debate. It's also my understanding that Mac PC's and Android phones already use this technology and MS is just playing catch up.

Thats exactly my opinion too. Should have been like that from first release of win 11. Whats the point having decent cpu, if such a simple task cant utilize the CPU?

FrancoDT · May 9, 2026

Thorenzz said:
Thats exactly my opinion too. Should have been like that from first release of win 11. Whats the point having decent cpu, if such a simple task cant utilize the CPU?

Yup, how often does someone burnout a CPU? Might as well put it to use and get your moneys worth, same goes for that RAM. CPU's are designed to operate under 100% load for extended periods and most users replace their computer in 5-7 years due to obsolescence long before a CPU failure would be a concern.

spectrumfox · May 9, 2026

Those are all fair assessments.

I just enabled the two ID's and rebooted, but I'm not sure I can tell any difference.

uncyler825 · May 9, 2026

spectrumfox said:
Those are all fair assessments.

I just enabled the two ID's and rebooted, but I'm not sure I can tell any difference.

If your hardware is high-end, you may not be able to perceive the difference. This difference is most noticeable on lower-performance PCs.

FrancoDT · May 9, 2026

Just an odd observation after re-enabling low latency mode on my beta machine it disabled my new run dialog box so I'm back to the old style dialog box. Guess I'll have to decide which I want to keep on it.

FrancoDT · May 9, 2026

Never mind, it looks like Microsoft pulled the new run dialog box and switch again even if you use the four vivetool codes.

spectrumfox · May 9, 2026

FrancoDT said:
Never mind, it looks like Microsoft pulled the new run dialog box and switch again even if you use the four vivetool codes.

I've still got New Run.

FrancoDT · May 9, 2026

spectrumfox said:
I've still got New Run.

You may not for long though but we'll see. It all just suddenly disappeared after a reboot for me and can't be re-enabled.

spectrumfox · May 9, 2026

FrancoDT said:
You may not for long though but we'll see. It all just suddenly disappeared after a reboot for me and can't be re-enabled.

Eh, oh well. It needs some working on anyway.

gauntlet0 · May 10, 2026

I'm having a major sound issue with 26220.8370. It is automatically muting my sound. I can adjust the slider and I get the "bong" sounds but then windows immediately mutes the audio. In looking at the sound settings the volume is set to -2147483648. I uninstalled the update, but then of course windows just reinstalled it again. Quite frustrating. I've tried all the wound settings and driver review and updates. Nothing is working.

Thorenzz · May 10, 2026

FrancoDT said:
Just an odd observation after re-enabling low latency mode on my beta machine it disabled my new run dialog box so I'm back to the old style dialog box. Guess I'll have to decide which I want to keep on it.

U seem to have a wierd issues with this build.

. For me, even after enabling low latency, my new run dialog still works fine.

Thorenzz · May 10, 2026

spectrumfox said:
Those are all fair assessments.

I just enabled the two ID's and rebooted, but I'm not sure I can tell any difference.

Yeah with your 9950x3d beast u probably wont see any difference. But on my laptop with 5600H the difference is noticable.

waltc · May 10, 2026

26220.8370 Installed without difficulty. In keeping with the thread topics so far, CPUs will not "burn out" using a lower-latency boot mode for Windows...

(That sounds like the usual Apple anti-Windows propaganda...

) If the CPU isn't designed to run at those latencies, then regardless of what the software asks for it will not do it because it can't--all this means is that Microsoft is trying to get better boot-to-full-desktop speeds in Windows. It seems to be working as I have a lot of desktop short-cuts, and from the first time I booted with this build I noticed that the usual "refresh" of the shortcut icons went much faster than it has been doing for quite some time, now! If that continues I will be very pleased.

EDIT: After looking into this a bit more, I've rarely seen a performance feature explained as poorly as this one, and so no wonder it's been so widely misunderstood. It's really a matter of Microsoft simply using the CPU in its Windows software more efficiently--that is, getting more of the performance your CPU is designed to deliver out of it when running Windows. People expect the CPU and GPU to max out when running their games for hours at a time, because that is what CPUs and GPUs are designed to do! Running the CPU or GPU a max performance is not doing anything weird or strange to the CPU or GPU--it is simply utilizing the top performance of the CPU/GPU that users expect to see when they buy them. Running games and benchmarks that max out the performance of your CPU or GPU is what people expect. It's no different with Windows. People calling this "brute force" and so on, as if it's somehow "odd" or unusual, don't know what they are talking about...

Obviously. It's just Windows using your CPU more efficiently at certain times. That's all there is to it. Ho-hum. I'm glad to see it!...

(Wanted to add: I tried the new Administrator mode since all I had to do was enable it from Account Protection, and it worked. However, it refused to allow immediate sign-in access after the desktop had fully booted, as I had to enter my password again for two separate files, and after I did that I got a bizarre warning about Edge--which I don't use--and then I was in, no further problems. I am going to reboot again to see if the initial improvement to latencies at boot and the Admin mode behave as advertised.)

EDIT: I have turned off this newer Admin mode because I don't like it. It throws up prompts asking for my password which UAC never does--not even prompts! I have reverted to my original settings, accordingly. I think it is a nice touch for people who want more control over their security than the standard Administrator modes provide, however. I just don't need it.

~~If things change in subsequent reboots I'll add the info here.~~ Done..

Thorenzz · May 10, 2026

waltc said:
26220.8370 Installed without difficulty. In keeping with the thread topics so far, CPUs will not "burn out" using a lower-latency boot mode for Windows... (That sounds like the usual Apple anti-Windows propaganda...) If the CPU isn't designed to run at those latencies, then regardless of what the software asks for it will not do it because it can't--all this means is that Microsoft is trying to get better boot-to-full-desktop speeds in Windows. It seems to be working as I have a lot of desktop short-cuts, and from the first time I booted with this build I noticed that the usual "refresh" of the shortcut icons went much faster than it has been doing for quite some time, now! If that continues I will be very pleased.

EDIT: After looking into this a bit more, I've rarely seen a performance feature explained as poorly as this one, and so no wonder it's been so widely misunderstood. It's really a matter of Microsoft simply using the CPU in its Windows software more efficiently--that is, getting more of the performance your CPU is designed to deliver out of it when running Windows. People expect the CPU and GPU to max out when running their games for hours at a time, because that is what CPUs and GPUs are designed to do! Running the CPU or GPU a max performance is not doing anything weird or strange to the CPU or GPU--it is simply utilizing the top performance of the CPU/GPU that users expect to see when they buy them. Running games and benchmarks that max out the performance of your CPU or GPU is what people expect. It's no different with Windows. People calling this "brute force" and so on, as if it's somehow "odd" or unusual, don't know what they are talking about... Obviously. It's just Windows using your CPU more efficiently at certain times. That's all there is to it. Ho-hum. I'm glad to see it!...

(Wanted to add: I tried the new Administrator mode since all I had to do was enable it from Account Protection, and it worked. However, it refused to allow immediate sign-in access after the desktop had fully booted, as I had to enter my password again for two separate files, and after I did that I got a bizarre warning about Edge--which I don't use--and then I was in, no further problems. I am going to reboot again to see if the initial improvement to latencies at boot and the Admin mode behave as advertised.)

EDIT: I have turned off this newer Admin mode because I don't like it. It throws up prompts asking for my password which UAC never does--not even prompts! I have reverted to my original settings, accordingly. I think it is a nice touch for people who want more control over their security than the standard Administrator modes provide, however. I just don't need it.

~~If things change in subsequent reboots I'll add the info here.~~ Done..

Really well said and explained.

Its something what microsoft should have done to start with win 11, and not adding it after years and bragging about it to make massive confusion among users who dont really understand how it works. They should have said "improved load times of explorer and boot times" and force enable it for everyone. Now they just put wood into the fire for windows haters... They only made it worse for them self, and not explaining whats really going on.

FrancoDT · May 10, 2026

Thorenzz said:
U seem to have a wierd issues with this build. . For me, even after enabling low latency, my new run dialog still works fine.

This is per Co-Pilot so won't swear to it's accuracy but:

What happened on

On 26220.8370, Microsoft removed the entire Run‑dialog feature bundle from the OS payload:

What was removed:

The four feature IDs (57156807, 57259990, 58527096, 58381341)
The XAML host for the modern Run dialog
The Settings page hook that shows the toggle
The shell activation handler for Win+R that routed to the new UI
This means:
- ViVeTool cannot re‑enable it
- The Settings toggle cannot reappear
- Win+R must fall back to the classic dialog
- Even if you previously enabled it, the feature disappears after updating to 26220.8370 because the binaries are gone
This is not a rollout issue — it’s a payload removal.

spectrumfox · May 10, 2026

FrancoDT said:
This is per Co-Pilot so won't swear to it's accuracy but:

What happened on
On 26220.8370, Microsoft removed the entire Run‑dialog feature bundle from the OS payload:

What was removed:

The four feature IDs (57156807, 57259990, 58527096, 58381341)

The XAML host for the modern Run dialog

The Settings page hook that shows the toggle

The shell activation handler for Win+R that routed to the new UI

This means:

ViVeTool cannot re‑enable it

The Settings toggle cannot reappear

Win+R must fall back to the classic dialog

Even if you previously enabled it, the feature disappears after updating to 26220.8370 because the binaries are gone

This is not a rollout issue — it’s a payload removal.

That's not accurate as I still have New/Modern Run and it's survived multiple reboots since installing .8370.

Copilot sucks.

FrancoDT · May 10, 2026

spectrumfox said:
That's not accurate as I still have New/Modern Run and it's survived multiple reboots since installing .8370.

Copilot sucks.

View attachment 171136
View attachment 171137

Couldn't say, it might be getting pulled in stages. I just know it completely disappeared on my machine and the vivetool codes can't re-enable it now. That's the only explanation I could find.

Someone on the Dev build in the tutorial thread for this mod also mentioned he couldn't enable it with the four vivetool codes as well.

Thorenzz · May 11, 2026

FrancoDT said:
Couldn't say, it might be getting pulled in stages. I just know it completely disappeared on my machine and the vivetool codes can't re-enable it now. That's the only explanation I could find.

Someone on the Dev build in the tutorial thread for this mod also mentioned he couldn't enable it with the four vivetool codes as well.

Same with me. I still have new Run and also toggle for it after multiple reboots. I also still have it on my WinToGo USB drive.

FrancoDT · May 11, 2026

waltc said:
EDIT: After looking into this a bit more, I've rarely seen a performance feature explained as poorly as this one, and so no wonder it's been so widely misunderstood. It's really a matter of Microsoft simply using the CPU in its Windows software more efficiently--that is, getting more of the performance your CPU is designed to deliver out of it when running Windows. People expect the CPU and GPU to max out when running their games for hours at a time, because that is what CPUs and GPUs are designed to do! Running the CPU or GPU a max performance is not doing anything weird or strange to the CPU or GPU--it is simply utilizing the top performance of the CPU/GPU that users expect to see when they buy them. Running games and benchmarks that max out the performance of your CPU or GPU is what people expect. It's no different with Windows. People calling this "brute force" and so on, as if it's somehow "odd" or unusual, don't know what they are talking about... Obviously. It's just Windows using your CPU more efficiently at certain times. That's all there is to it. Ho-hum. I'm glad to see it!...

Now, Microsoft VP Scott Hanselman has taken to X to respond to the trolls, explaining how and why this new Low Latency Profile feature is actually standard practice and overall beneficial to end users. "All modern operating systems do this, including macOS and Linux. It's not "cheating"; this is how modern systems make apps feel fast: they temporarily boost the CPU speed and prioritize interactive tasks to reduce latency."

https://www.windowscentral.com/gaming/indies-idxbox/terratech-legion-xbox-game-pass-preview

spectrumfox · May 12, 2026

FrancoDT said:
Now, Microsoft VP Scott Hanselman has taken to X to respond to the trolls, explaining how and why this new Low Latency Profile feature is actually standard practice and overall beneficial to end users. "All modern operating systems do this, including macOS and Linux. It's not "cheating"; this is how modern systems make apps feel fast: they temporarily boost the CPU speed and prioritize interactive tasks to reduce latency."

https://www.windowscentral.com/gaming/indies-idxbox/terratech-legion-xbox-game-pass-preview

Taking to Twitter to respond to trolls never ends well, since that's the majority of its userbase now...

Insider KB5089417 Windows 11 Insider Beta (25H2) build 26220.8370 - May 8

Changes and improvements gradually being rolled out with toggle on​

[EDU]​

[Administrator Protection]​

[Other]​

Reminders for Windows Insiders in the Beta Channel (Soon transitioning to the new Beta experience)​

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

Attachments

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

What happened on​

What was removed:​

My Computers

Well-known member

What happened on​

What was removed:​

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Similar threads

Changes and improvements gradually being rolled out with toggle on

[EDU]

[Administrator Protection]

[Other]

Reminders for Windows Insiders in the Beta Channel (Soon transitioning to the new Beta experience)

What happened on

What was removed:

What happened on

What was removed: