Microsoft released two new Windows 10 Preview builds today, the 20H1 build 18860 for Skip Ahead Insiders, as well as the 19H1 build 18362 for Insiders on the Fast Ring. Microsoft is now almost done with the 19H1 update, but this new build fixes a single issue causing the Connect app to crash in some cases. Microsoft still has to fix some known issues related to anti-cheat software and Creative X-Fi sound cards, but the list of bugs is getting shorter with every new update.
You can find the full release notes for the build 18362 below:
General changes, improvements, and fixes for PC
We fixed an issue resulting in the Connect app crashing on launch for some Insiders.
- Launching games that use anti-cheat software may trigger a bugcheck (GSOD).
- Creative X-Fi sound cards are not functioning properly. We are partnering with Creative to resolve this issue.
Some Realtek SD card readers are not functioning properly. We are investigating the issue.
Known issues for Developers
- If you install any of the recent builds from the Fast ring and switch to the Slow ring, optional content such as enabling developer mode will fail. You will have to remain in the Fast ring to add/install/enable optional content. This is because optional content will only install on builds approved for specific rings.
The Windows 10 19H1 update is expected to start rolling out in April if everything goes well, and it shouldn’t be too long before Release Preview Insiders receive their first 19H1 build. Sound off in the comments if you think the 19H1 update is already stable enough to be used on your main PC.
Update: Microsoft has updated the release notes to remove the issue causing Microsoft Store app updates to not automatically install on build 18356+, and we’ve now removed it from our post, too. Brandon LeBlanc from the Windows Insider team confirmed on Twitter that this bug has been fixed in this build.
Further reading: 19H1, build 18362, Fast Ring, Windows 10, Windows Insider
Heads up guys – we updated the blog post for Build 18362 as I actually just got confirmation that the Microsoft Store bug you guys were talking about is indeed *fixed*. Sorry about that.
— Brandon LeBlanc (@brandonleblanc) March 20, 2019