\n
This afternoon (Redmond time) Microsoft has just released Windows Insider build 18985 for 20H1 Fast Ring insiders. Along with an updated Bluetooth pairing experience and an update to the Snip & Sketch screen capture app, the company has released a list of fixes coming to 18985, including some fixes to the new Cloud Download option for resetting Windows 10 PCs, Task Manager fixes, and what appears to be final resolution of the longstanding Realtek SD card reader known issue. Here’s the full list of “changes, improvements and fixes for PC” for build 18985:
\n
\n
\n
- We fixed an issue where adding a new Language Pack reported successful installation but was not installed.
\n
- We fixed an issue impacting the reliability of Settings when accessing the Network & Internet section.
\n
- We fixed an issue that could result in printer entries not displaying properly for non-admin accounts—the text overlapping, and not being clickable.
\n
- We fixed an issue resulting in Task Manager showing an unexpectedly high temperature for certain GPUs.
\n
- We fixed an issue resulting in Task Manger unexpectedly showing 0% CPU usage in the Performance tab.
\n
- We fixed an issue where the setting that enables Microsoft accounts on your device to go Passwordless (by requiring Windows Hello sign in and hiding the password option from the lock screen) was showing for local account users. Now the setting will only show for Microsoft account users.
\n
- We fixed an issue with the Reset this PC cloud download option not calculating the correct amount of space you needed to free up if you did not have enough disk space to proceed.
\n
- We fixed an issue with the Reset this PC cloud download option not working when specific optional features were installed.
\n
- At this time, we’re removing our known issue about Realtek SD card readers. If you are still encountering issues with any SD cards, please take a moment to check for driver updates, and file feedback if that does not resolve it for you.
\n
\n
\n
You might think that the list of known issues is a bit smaller this time without the ubiquitous Realtek Card Reader issue, and you’d be right. From the sounds of it, the problems with anti-cheat software, which require work from game developers to update their game software after changes to Windows 10, are close to being resolved, as well. Microsoft says it’s working with game developers to “minimize the likelihood of these issues in the future.” However, some apparently new issues are cropping up regarding Windows Mixed Reality. Here’s the full list of known issues:
\n
\n
\n
- 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.
\n
- Certain 2D apps (like Feedback Hub, Microsoft Store, 3D Viewer) are incorrectly being treated as having protected content within Windows Mixed Reality. During video capture, these 2D apps block their content from being recorded.
\n
- When capturing a repro video while filing a bug via Feedback Hub in Windows Mixed Reality, you won’t be able to select Stop video, due to the protected content issue noted above. If you want to submit a repro video, you will need to wait 5 minutes for the recording to time out. If you’d like to file the bug without a repro video, you can close the Feedback Hub window to end the recording and resume filing your bug when you reopen the app in Feedback > Drafts.
\n
- When viewing Optional drivers in the new section on the Windows Update page, you may notice older drivers showing as available for download. If accepted, they will attempt to install and fail to do so. This is a bug related to revised Windows Update detection logic rather than this new UI. The root cause is understood, and a fix will be available in an upcoming build.
\n
\n
\n
We’re expecting to hear from the 19H2 side of things soon, too, as it’s been a while since we’ve had a 19H2 build, but for now, if you’re a Windows Insider on the 20H1 Fast Ring, get to downloading now!
\n
\n
\n\nFurther reading: 20H1, build 18985, Fast Ring, Windows 10, Windows Insider