Tip o’ the Week 384 – Insiders Update 16215

clip_image001The Windows Insider program has over 10m participants, and after the release of the Creators Update, the heat is being turned up again as the Windows 10 Fall Creators Update starts testing.

If you’re an Insider on the Fast Ring, you can get hold of the newly-released build 16215, which contains a load of new functionality – for some more detail of what to expect, read here or see this.

There are myriad UI changes, many of them quite subtle, and Edge browser gets some interesting new features (and some returning ones) – more details here. Full release notes for the build are here.


As ever, there are a few known issues documented in the release notes. In this build, If you have multiple displays at different scale resolutions, Edge may habitually load pages at the wrong scale – so everything is either really really tiny
or absolutely massive.

To workaround this, just flick to another tab and back again – and save constantly zooming in and out.

Another issue to be aware of is that after installation of 16215, you may find that Outlook won’t connect to your mailbox any more – and any attempts to create a new profile will fail.

Repairing / reinstalling Office won’t help either. Instead of going through the aggro, try a quick fix in disabling HTTP/2 on the machine:

  • Open Registry Editor (WindowsKey+R regedit)
  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
  • Add a new DWORD value, called EnableDefaultHttp2 - default value will be 0x00000000 – that’s fine.
  • Now repeat by adding the same value, at: HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp
  • Reboot. Bob’s your uncle. Enjoy.
Comments (1)

  1. Antti Nivala says:

    We are facing a similar-looking issue with a client application that uses RPC over HTTP (with SSL/TLS). After installing Windows 10 version 1709 (Fall Creator’s Update), the client application can no longer communicate with the application’s server part. This has ben reproduced on a large number of machines. Interestingly, this only happens for the service that is running under the Local System identity. For the parts of the application that run with other user identities, this problem does not occur.

    When tracing the network traffic we noticed that when running under Local System identity, the RPC subsystem is trying to establish communication as HTTP/2. The server accepts that, but then at a later point the server returns the error “HTTP 1.1 required” and communication stops. When running under normal user identity, the RPC subsystem does not try to use HTTP/2 and everything works fine.

    We can work around the problem by either disabling HTTP/2 on the server side in IIS 10.0 (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters, EnableHttp2Tls = 0) or on the client side by setting EnableDefaultHttp2 to 0 as you suggest above.

    Does this sound like the same issue as what you had with Outlook in 16215? What did you do to resolve that?

Skip to main content