KB5001330 Windows 10 Insider Beta 19043.928 21H1 and RP 19042.928 20H2 Insider

@Globespy,

Maybe something went amiss in your first install. I would let Windows install it again, but to play it safe, have a system image backup ready before just in case.

f14tomcat said:

My gut feel is if you click Install, it's gonna go real fast and basically do nothing.

Reboot first and see if it comes back.

TC,
Thanks for the reply.
I tried to hide it with the tool, but it wasn't having any of that, even though the tool seemed to think it had hidden it!
I hit install and it took close to 20 minutes, stuck at 74% for the longest part of that time.
It finished without error, and didn't even ask for a restart.
I hope that it's not going to pop up next time I go to update, but for today I'm leaving it as is.

I can confirm that after doing a clean install today of 20H2 that the things that were broken by the 21H1 April updates are working again.

Technically not an Insider, but I did go from 20H2 to 21H1 19043.899 using the enablement package method, and also got stuck there like some others have reported. None of the usual tricks (DISM, reset WU, manual KB install etc) worked for me either.

Downloaded the .906 ISO from UUP Dump and did an In Place upgrade as has been suggested.

Just posting to confirm that it went quickly and smoothly, problem solved. Got a couple of .NET updates and the latest KB5001330 automatically from WU straight afterwards. Sitting at 19043.928 now, and all is working perfectly.

Looks like MS goofed up twice in a row ... !
New Windows 10 update is causing a whole world of pain | TechRadar

Ohmer said:

Technically not an Insider, but I did go from 20H2 to 21H1 19043.899 using the enablement package method, and also got stuck there like some others have reported. None of the usual tricks (DISM, reset WU, manual KB install etc) worked for me either.

Downloaded the .906 ISO from UUP Dump and did an In Place upgrade as has been suggested.

Just posting to confirm that it went quickly and smoothly, problem solved. Got a couple of .NET updates and the latest KB5001330 automatically from WU straight afterwards. Sitting at 19043.928 now, and all is working perfectly.

Yes I think .899 update screwed up Windows Update