This week's Windows 10 build for the Fast ring came a little later than usual, after last week's was earlier than Microsoft's typical schedule. Build 18936 includes a handful of improvements to Your Phone, the calendar flyout, and more, but there's also a fairly long list of fixes, as well as some known issues to be aware of.
Among the small improvement in today's build is the ability to run Windows Sandbox without administrator privileges, as well as a fix for an issue that could prevent users from installing games through the Xbox app. Here's the full list:
- We fixed an issue that was causing failures when installing games via the Xbox app in the previous flight.
- We fixed an issue resulting in the Photos live tile potentially drawing outside the bounds of the tile.
- We fixed an issue where the emoji panel would crash when high contrast was enabled.
- We updated the disk type text in Task Manager’s Performance tab to now match the size of the other subtext on that tab.
- We fixed an issue resulting in items not launching in the foreground when selected from the taskbar jump list of certain apps.
- We fixed an issue that could result in the virtual desktop thumbnail in task view not updating after moving a window to a different desktop.
- Running Windows Sandbox no longer requires Administrator privilege.
- We fixed an issue resulting in the composition string not being shown in certain apps when typing with the Japanese IME.
- We fixed an issue resulting in certain apps crashing when typing with the Chinese Pinyin IME.
- We fixed an issue resulting in certain games unexpectedly just showing a black screen when run in full screen mode on some devices recently.
Of course, even with those fixes, there are a few known issues with this release, many of which are new. One of them might actually bar you from installing the build, and there's no workaround, so you'll need to wait for a fix.
- A limited number Insiders attempting to install Build 18936 may experience install failures with error code c1900101 due to a compatibility bug with a storage driver on their device. The device will attempt to install, fail, and successfully roll back to the currently installed build on the device. Attempted re-tries to install the build, either manual or automatic, will not bypass this issue. A fix is forthcoming, but there are no known workarounds currently. Note: By default, the update will attempt to install (3) times. Users may pause updates if they experience this issue and want to bypass the re-try attempts.
- Insiders may notice some changes in Magnifier with today’s build. These aren’t quite ready yet for you to try, but we’ll let you know once they are in an upcoming flight.
- There has been an issue with older versions of anti-cheat software used with games where after updating to the latest 19H1 Insider Preview builds may cause PCs to experience crashes. We are working with partners on getting their software updated with a fix, and most games have released patches to prevent PCs from experiencing this issue. To minimize the chance of running into this issue, please make sure you are running the latest version of your games before attempting to update the operating system. We are also working with anti-cheat and game developers to resolve similar issues that may arise with the 20H1 Insider Preview builds and will work to minimize the likelihood of these issues in the future.
- Some Realtek SD card readers are not functioning properly. We are investigating the issue.
- Tamper Protection may be turned off in Windows Security after updating to this build. You can turn it back on. In August, Tamper Protection will return to being on by default for all Insiders.
As we always note, this build is part of the 20H1 development cycle, and it's leading up to a feature update to be released in the first half of next year. That means we're still fairly early into the development cycle, and the new features may not justify the bugs you might find. If you'd rather try the upcoming 19H2 feature update, that one is now in the Slow ring, and it should be less problematic.
0 Comments - Add comment