Microsoft have pushed out their 2nd 20H1 fast ring build of the week. Build 19030 once again just contains bug fixes but it does remove the watermark from the right hand corner of the desktop. Microsoft say this doesn’t mean they are done but it does mean we are close to completion of the 20H1 phase of Windows 10.
The known issues still include the USB C drive issue and the BattlEye ant-cheat software issue. Here are the changes and the known issues:
General changes, improvements, and fixes for PC
The build watermark at the lower right-hand corner of the desktop is no longer present in this build. This doesn’t mean we’re done…
We fixed an issue where if you started to reset your MSA pin from the sign-in screen and left it without interacting with it for some time, it would result in a black screen, requiring a reboot to recover.
We fixed an issue that could result in night light settings getting lost on the primary monitor when the system is connected/disconnected from a secondary monitor.
We fixed an issue that could result in an out of memory message when watching a long HEVC video.
We fixed an issue resulting in certain apps not fully filling the screen when maximized in recent builds.
BattlEye and Microsoft have found incompatibility issues due to changes in the operating system between some Insider Preview builds and certain versions of BattlEye anti-cheat software. To safeguard Insiders who might have these versions installed on their PC, we have applied a compatibility hold on these devices from being offered affected builds of Windows Insider Preview. See this article for details.
We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
We’ve heard that Settings still isn’t available outside of launching via the URI (ms-settings:) for some Insiders and are investigating.
Some Insiders are reporting that after successfully installing printer drivers from the Optional Updates section, the same driver is still showing as available for install. We’re looking into the issue.
We’re looking into reports of certain external USB 3.0 drives not responding with Start Code 10 or 38 after they’re attached.