Insider KB5077221 Windows 11 Insider Canary build 28020.1611 (26H1) - Feb. 12

OAT · Feb 13, 2026

Edwin said:
Got the new Run box but, it constantly crashes!

View attachment 163205

Thanks, I had not tried.
Same thing happened in Dev. So it should be OK in the next Canary build.

I don't really get it anymore, why is Canary catching up to Dev?
Shouldn't Canary be the testing ground?

Edwin · Feb 13, 2026

OAT said:
I had not tried.

It crashes as soon as you type a special character, eg. %temp% or shell:

And..., I don't like that fact that you can't drag the box around.

OAT · Feb 13, 2026

Edwin said:
It crashes as soon as you type a special character, eg. %temp% or shell:

Yeah, that quickly can become a pain.

Edwin · Feb 13, 2026

Helmut!!!
It didn't even wipe out any dinosaur, 'ported' system components!!!

or, any special reg entries!!!

OAT · Feb 13, 2026

Edwin said:
Helmut!!!
It didn't even wipe out any dinosaur, 'ported' system components!!!

or, any special reg entries!!!

I had to put back the exclusion for Winaero though.

Edwin · Feb 13, 2026

OAT said:
I had to put back the exclusion for Winaero though.

Really? Mine stayed.

OAT · Feb 13, 2026

Edwin said:
Really? Mine stayed.

Then I must have never set it. That must be it.
Most of my time is set on Dev now.
Is uwd2 still working ok for you?

Edwin · Feb 13, 2026

OAT said:
Is uwd2 still working ok for you?

Ah! That was the other thing..., yes it is, but, I had to re-add it to the All Users startup folder!

Imhelpingyoubro · Feb 13, 2026

I’m having a persistent issue with installing Windows 11 Build 28020.1611.

Every time Windows Update tries to install it, the installation fails with error (0xc1900101) and the system rolls back to the previous build.

Here’s what I’ve already tried:

- Restarting the system multiple times
- Disconnecting all external devices (USB drives, peripherals, etc.)
- Disconnecting my secondary HDD to rule out storage-related issues
- Replacing Intel SATA/AHCI controller drivers with the default Microsoft drivers (Device Manager → “Let me pick from a list”)
- Resetting Windows Update components
- Stopping Windows Update, BITS, CryptSvc, and TrustedInstaller services
- Clearing SoftwareDistribution and catroot2
- Checking for pending.xml (it wasn’t present)
- Attempting to trigger the update again manually

None of these steps helped — the update always fails with 0xc1900101 and reverts back.

I’ve paused updates for 7 days to avoid repeated installation attempts.

My question:
Is this a known issue with Build 28020.1611, and should I simply wait for the next Canary build (e.g., 28020.1612 or 28021) to resolve the problem? :Rolleyes:

OAT · Feb 13, 2026

Imhelpingyoubro said:
None of these steps helped — the update always fails with 0xc1900101 and reverts back.

I’ve paused updates for 7 days to avoid repeated installation attempts.

My question:
Is this a known issue with Build 28020.1611, and should I simply wait for the next Canary build (e.g., 28020.1612 or 28021) to resolve the problem? :Rolleyes:

Well, not a known issue until now. It sure does not mean it is not an issue.
And you have ran the mandatory SFC & DISM commands? (not listed above)
Have you tried an in place repair using WU? Bottom one on the screenshot.

Imhelpingyoubro · Feb 13, 2026

When I finish my work, I will try these methods and post the results here. To be honest, Microsoft Copilot did not suggest what you did.

Imhelpingyoubro · Feb 13, 2026

@OAT

And I cleaned everything using the tool (Disk Cleanup). Now I'll try to install this update and restart the computer.

Imhelpingyoubro · Feb 13, 2026

Unfortunately, as you can see, it didn't help at all. Should I create an external drive with this update and force it?

garlin · Feb 14, 2026

fg2001gf11F said:
In my case I had the same issue on 2 machines Dell XPS 8930 and Dell XPS 8940. Both are in multiboot with other Builds. The other builds boot fine with WinRE.
I also tried a repair update in place with ISO created from UUP-dump but I ended up with the same issue.
I did not have this problem on 2 other machines. GMKtec M2 and GMKtec K3 which are mini PCs.

So, I restored a backup of Build 28020.1546 and found out that the problem was already in the previous Build too.
I don't know at this point when the problem exactly started, but it is definitely also in previous build 28020.1546 and now the same with 28020.1611.

Same exact problem on Both Dell desktops. XPS 8930 and XPS 8940.
View attachment 163163

Edit:
Definitely something wrong with the signature.
WinRE boots fine if I disable secure boot in the UEFI BIOS.

Same happens also after a clean install of 28020.1611 on the same Dell Desktops.

Note: there two different winload.efi files, one used by the normal OS boot and the other used by WinRE.
The signature issue is with the one used by WinRE.

You should be able to mount WinRE by assigning it a drive letter from diskpart.

Browse to the WinRE filesystem, ie. R:\Windows\System32\winload.efi
Copy it to C:\ somewhere.

Compare the two files, in theory they're supposed to be in sync. Also check the Properties / Digital Signature and open the cert. Are they signed PCA 2011 or UEFI CA 2023?

On a clean install, the winload.efi should be the same for install.wim & winre.wim. But if you're getting Insider updates, the update process should be patching WinRE as necessary (same thing happens to normal Production channel). Which means those two files should be in sync!

fg2001gf11F · Feb 14, 2026

garlin said:
You should be able to mount WinRE by assigning it a drive letter from diskpart.

Browse to the WinRE filesystem, ie. R:\Windows\System32\winload.efi
Copy it to C:\ somewhere.

Compare the two files, in theory they're supposed to be in sync. Also check the Properties / Digital Signature and open the cert. Are they signed PCA 2011 or UEFI CA 2023?

On a clean install, the winload.efi should be the same for install.wim & winre.wim. But if you're getting Insider updates, the update process should be patching WinRE as necessary (same thing happens to normal Production channel). Which means those two files should be in sync!

@garlin,
Something is weird.

Here is what I see on the certificate for winload.efi in WinRE.
Microsoft Development PCA 2014? Looks like DELL firmware on my 2 machines XPS 8940 and XPS 8930 does not have updates to accept that certificate even if it has a valid signature.

While this one is for the normal windows boot. Microsoft Windows Production PCA 2011.

garlin · Feb 14, 2026

Check the Embedded Signature. At the Windows level, other MS signing certs exist in the Windows cert store (with other dates).

fg2001gf11F · Feb 14, 2026

garlin said:
Check the Embedded Signature. At the Windows level, other MS signing certs exist in the Windows cert store (with other dates).

Sorry, I don't know where to find the Windows cert store and what to look for.
I think the problem is between Microsoft and Dell.
I don't have that WinRE error on the GMKtec devices, just on DELL desktops XPS 8940 and XPS 8930.

VegetaTarble · Feb 14, 2026

mine installed perfectly, no errors thus far. will report any if found.

garlin · Feb 14, 2026

fg2001gf11F said:
I think the problem is between Microsoft and Dell.
I don't have that WinRE error on the GMKtec devices, just on DELL desktops XPS 8940 and XPS 8930.

No, I meant in your original screenshot, you selected the Catalog cert (bottom one), instead of the Embedded Signature cert (top one) to view.

Imhelpingyoubro · Feb 14, 2026

@OAT @Brink

Can specialists tell me what the heck is going on here?

Help!

Insider KB5077221 Windows 11 Insider Canary build 28020.1611 (26H1) - Feb. 12

What’s new in Canary Build 28020.1611​

Changes and Improvements gradually being rolled out with toggle on*​

[Built-in Sysmon]​

[Windows Share]​

[General]​

Reminders for Windows Insiders in the Canary Channel​

In the end, it truly does not matter.

My Computers

♦ ♦

My Computers

In the end, it truly does not matter.

My Computers

♦ ♦

My Computers

In the end, it truly does not matter.

My Computers

♦ ♦

My Computers

In the end, it truly does not matter.

My Computers

♦ ♦

My Computers

Active member

Attachments

My Computer

In the end, it truly does not matter.

My Computers

Active member

My Computer

Active member

My Computer

Active member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Active member

My Computers

Well-known member

My Computer

Active member

My Computer

Similar threads

What’s new in Canary Build 28020.1611

Changes and Improvements gradually being rolled out with toggle on*

[Built-in Sysmon]

[Windows Share]

[General]

Reminders for Windows Insiders in the Canary Channel