We have implemented the workaround mentioned above and it seems to be working for us. Obviously disabling HTTP/2 is not an ideal fix. Hopefully MS will release an update on this soon? And does anyone know if a potential fix would be issued as a "patch Tuesday" style Windows update (out-of-band or otherwise), or would it come as a VS 2019 update?
Is the http.sys file at issue part of Windows in general, or VS specific?