It’s been quite a while since we’ve seen a Fast Ring Windows Insider build, but Dona Sarkar and the Windows Insider team have finally released a new build. As usual, these builds are not perfect, so please have a look at the following known issues, changes, and improvements before you proceed with installation on your device.
Changes, improvements, and fixes for PC
There are tons of changes, improvements, and fixes for PC in this build, so we’re selecting a few for you below. Please check out the full list here.
- If you were impacted by the issue causing your upgrade to get stuck or hung at around 33% trying to update to Build 16215, we fixed the issue and you should be able to upgrade to this build (Build 16226) without getting stuck at 33%.
- We fixed the issue causing PCs to bugcheck (GSOD) with inaccessible boot device on install, and the Windows Update error 0x80070643 after rollback.
- We fixed an issue preventing PDFs from opening in Microsoft Edge on some devices with enterprise configurations.
- We fixed the issue causing some PDFs and sites to open in a cropped view (zoomed in) in Microsoft Edge, causing part of the content to be inaccessible to the user.
- We fixed an issue from the previous flight where accented characters couldn’t be input properly into Win32 apps using the hardware keyboard.
- We fixed a Hyper-V issue resulting in some Insiders not being able to connect to VMs in the last flight.
- We fixed an issue resulting in Start now working for a small percent of Insiders on the last flight.
- We’ve adjusted the application of Fluent Design in Start and Action Center to now be a touch more transparent and let more of the underlying color through. Along the way we also updated the Action Center to use the newer conscientious XAML scrollbar design.
- We fixed an issue from the previous flight wherein you couldn’t expand notifications displayed in the Action Center
- We fixed an issue resulting in some inbox apps unexpectedly appearing to be missing after upgrading to 16215 (although Store said they were installed)./li>
- Snipping tool is now natively per-monitor DPI aware! That means it should no longer be blurry when used in mixed DPI environments, or when changing DPI.
- We’ve gone through all our image resource files and removed unneeded XMP metadata.
- We fixed an issue where some of the older control panel dialogs were unexpectedly showing grey sections instead of white.
- We fixed an issue from recent flights where selecting “Restart” in the power options list with a pending update had the same effect as “Restart and Update”.
- When you right-click the network icon in the system tray, “Open Network and Sharing Center” will now open Network & Internet Settings
- We fixed an issue where the Start Fresh page was included in Microsoft Edge’s recovery store, leading to potentially multiple Start Fresh pages being visible in each window after Microsoft Edge was reopened.
— Dona Sarkar (@donasarkar) June 21, 2017
Known issues for PC
- If you have the .NET 3.5 Framework installed, updating to this build may fail and roll back to the previous build. As a workaround, uninstall .NET 3.5 before trying to update to this build and then reinstall .NET 3.5 after you update to this build. For more info, see this forum post.
- Auto-complete in URL bar of Microsoft Edge may fail on some devices, searching for a partial string instead of the autocompleted text picture. This issue will be fixed in an upcoming flight.
- Some UWP apps such as Twitter will crash on launch.
- Word 2016 will crash if you try to ink on it.
- You may notice some of your inbox apps are now displaying a name that looks like “ms-resource:” and are listed at the bottom of Start. We’re investigating. In the meantime, the app should still launch normally, it’s only the name resource that’s impacted.
- We’re investigating your reports that the battery status on certain laptops isn’t updating while the device is unplugged.
As always, we invite you to let us know your thoughts on this latest build by dropping us a comment below. And please continue to submit your feedback via the FeedBack Hub so Microsoft can correct your issues.