That's a bad update from Microsoft. It's been discussed here:
Some workarounds are uninstalling the updates or disabling HTTP/2 from registry. Some users report different results for the same workaround. Hopefully Microsoft will fix this mess soon.
That's a bad update from Microsoft. It's been discussed here:
Some workarounds are uninstalling the updates or disabling HTTP/2 from registry. Some users report different results for the same workaround. Hopefully Microsoft will fix this mess soon.