[German]On 26.11.2019 Microsoft released the Windows 10 Insider Preview Build 19033 (20H1) in Fast Ring as well as in Slow Ring for insiders. The development branch 20H1 will end in spring 2020 as the new Windows 10 version 2004.
Fast Ring to get new development builds
After the 20H1 is nearing completion and the watermark of a previous build has been removed a few days ago, Microsoft will soon release new builds from the development department in Fast Ring. This means that Microsoft will soon be releasing builds from the RS_PRERELEASE development branch in the Fast Ring Insider Preview (currently only builds from the VB_RELEASE branch are available there). This also means that the desktop watermark will be returned with these builds. If you want to stay on Windows 10 20H1, check the Windows Insider settings and switch to the Slow Ring.
20H1 becomes Windows 10 Version 2004
This build of Windows 10 is released as version 2004. In the Windows Blog Microsoft explains the reason why the development branch 20H1 will be released in spring 2020 as Windows 10 version 2004. The version number 2004 was chosen because the version 2003 for this Windows 10 version could lead to confusion with the long-expired Windows Server 2003.
Windows 10 20H1 is finished
In Windows Blog Brandon LeBlanc explains that the watermark has been removed from this Windows Insider Preview (this was already the case with the predecessor). According to LeBlanc, this means that the development of this Windows 10 version has been completed. New insider builds are for troubleshooting purposes only. This confirms what I published at the end of October 2019 in the blog post “Does Microsoft change the Windows 10 RTM dates?” as a rumour: Microsoft wants to adjust the RTM release dates for Windows 10 builds in the future and complete feature updates at the end of the year (December) and in summer. However, it remains to be seen when the build will be generally released.
What’s fixed in Preview Build 19033
It’s a bug fix release because Microsoft is working towards the final. Microsoft lists the following fixes:
- We fixed an issue that could result in Settings crashing for some users if you navigated to About when in Safe Mode.
- We fixed an issue resulting in some paired Bluetooth audio devices unexpectedly displaying with a cellphone icon in Bluetooth Settings.
- We fixed an issue where preferred Focus Assist automatic rules settings weren’t persisting upgrade.
- We fixed an issue where pressing the WIN + P keyboard shortcut twice in a row could result in ShellExperienceHost crashing.
- We fixed an issue that could result in the Start menu crashing on launch if a Windows update was pending restart.
- We fixed an issue where if you were using night light and weren’t already signed into a Microsoft Account, and subsequently attached your MSA, it would result in night light no longer working.
- We fixed an issue where if you quickly toggled Magnifier on and back off in Settings it would result in Magnifier.exe crashing.
- At this point, we’re removing the known issue that Settings still isn’t available outside of launching via the URI (ms-settings:) – so far we have not seen any reports from Insiders in the Slow ring that bypassed the impacted build range. If you are in the Fast ring, were on the impacted build range, and are one of the few still experiencing this issue, you will need to reset your PC. We appreciate your patience.
- We fixed an issue where you wouldn’t be able to type Chinese punctuation with the Pinyin IME after moving focus to and from a password field.
- Some users may have experienced error 80092004 when attempting to install build 19025.1052. This was isolated to that specific Cumulative Update and should not prevent installing build 19033.
- We have fixed an issue resulting in Start Code 38 with certain external USB 3.0 drives.
In this build there are still the following known issues:
- 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.
- 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 after they’re attached.
Cookies helps to fund this blog: Cookie settings