Another suggestion that this is a bug in Windows Server 2016, relating to HTTPS/2 on IIS 10 - see https://forums.iis.net/post/2137486.aspx

Can someone on the IIS team please have a look?

Thanks