KB5003637 (and the new KB5004476) gives error "Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR" in web browser using Visual Studio 16.10.1. or 16.10.2.

Question

Hi,

After installing the automatic update KB5003637 3 days ago, building web apps using Visual Studio 16.10.1. or even latest update Visual Studio 16.10.2. produces the error "Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR" in web browser (Images, css, etc don't load properly anymore).

It is clear in my case uninstalling the KB5003637 solves the issue. The only problem is when wanting to update Windows 10 it installs that same update over and over again.
The option to exclude/hide the update isn't there anymore, so this is very annoying.

I'm not the only one experiencing this problem as you can find here: https://stackoverflow.com/questions/67911570/failed-to-load-resource-neterr-http2-protocol-error-for-react-app-after-upg/67934980?noredirect=1#comment120151946_67934980.

Also the new update KB5004476 (which replaced the previous update KB5003637) is causing the same error. When installed I get the exact same errors, uninstalling solves it instantly.

Please advise, something is really wrong with these updates.

UPDATE!
Microsoft finally released a fix that works for me, as you can read here (last post): https://developercommunity.visualstudio.com/t/Failed-to-load-resource:-net::ERR_HTTP2_/1446262?viewtype=all Installing the most recent update KB5004237 solves the problem in my case. No more "Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR" errors, no more “System Thread Exception not Handled” error so far too! Yay! :)

Thanks in advance!
Kind regards,
Lester De Meyer.

Answer 1

Hello,

Just chiming in after finding this thread via google. We are having the same problem here, as well. Two developers both reported they are getting BSOD errors starting around 6/16. Issue is the same: developer is hosting page locally in IIS, Visual Studio 2019, Google Chrome. Developer performs a page refresh and gets "System Thread Exception not Handled" in file "HTTP.sys" error.

I've already sunk a couple days into trying to troubleshoot this. Even issued one person a replacement computer, and he had the same problem on the new machine.

All machines are fully updated and patched, latest version of Windows 10 21H1, IIS, Chrome, and VS. One person reports that the crashes happen less frequently in Firefox, and also less often in Edge.

Suggestions? We have tried removing KB5003637 but it is not showing in our list of removable updates.

I found this other thread which seems to mention removing KB5004476 may also help: https://learn.microsoft.com/en-us/answers/questions/440339/kb5003637-and-the-new-kb5004476-gives-error-34fail.html

Thanks!

Answer 2

I tested this with a valid SSL certificate and host file entry to see if this would work, and it does not - same issue persists. So, only workarounds are to not use SSL, try to set protocol to HTTP/1.1 manually, disabled HTTP/2 on your PC entirely via registry, or uninstall the two patches:

wusa /uninstall /kb:5004476
wusa /uninstall /kb:5003637

It still doesn't look like these issues are listed in the Known Issues section, which is a bit disconcerting...
https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-20h2#1623msgdesc

EDIT: You must also now uninstall KB5003690 if you have it before the other two. In order:

wusa /uninstall /kb:5003690
wusa /uninstall /kb:5004476
wusa /uninstall /kb:5003637

Answer 3

I was going to comment on the StackOverflow chat but don't have the reputation. This is definitely not a Chrome-specific error, both my developers and myself have had the same exact issue across Edge and Firefox, including blue screen with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED in http.sys when refreshing quickly in any browser and those failures begin occurring.

This is also not ASP.NET Core specific, since I have experienced it with both ASP.NET MVC applications running on .NET Framework 4.8, as well as with ASP.NET Core applications running .net core 3.1.

I've also heard the theory that it's IIS specific (e.g., IISExpress), which is also incorrect since we host over IIS 10.0.

One thing that I think has been absent from these discussions is that we are using the IIS Development Certificate, or another similar self-signed certificate that has been added to the trust. This does only appear - so far - to be happening for website with that type of certificate deployed. KB5003637 has changes to http.sys and some other relevant files and assemblies, so it's most definitely a bug in their release.

Even if there was something that was meant to be subsequently changed by browsers or platforms, there is no reason why it's acceptable that the intermediary behavior would be blue screen crashes.

Answer 4

@CBT Admin : We are dealing with the same issues with about 7 developers! Glad a developer saw your comment! Hopefully it will be fixed soon?

Answer 5

Yes I have had this same KB5003637 security patch keep showing up and causing this issue. This is a major bug that needs some serious MS time assigned to fixing this issue.

Also I noticed that as soon as you take out KB5003637, it also uninstalls the Windows 10 Feature Update version 21H1? Really is this update dependant on this small Security Patch?

I guess we wait for some sort of feedback from Microsoft.