Windows 10 build 19546

Windows 10 build 19546 is the third Insider Preview build of Manganese. This build was released to Windows Insiders in the Fast Ring on 16 January 2020.

Changes

 * When Windows Insiders updated to this build at the time of its release, they got an updated version of Calculator, which came with a graphing mode. However, this feature is not bundled with the build itself. It would not come bundled with the operating system itself until build 19603.
 * General changes, improvements, and bug fixes listed in the official release announcement.

Bugs

 * You must use an IDE or SATA hard drive if you want to install this build in VMware, otherwise the setup won't be able to find the drive.
 * The BattlEye anti-cheat software has some incompatibility issues due to changes in the operating system between some Insider Preview builds and certain versions.
 * The cloud download recovery option is broken and thus it can't be used. The local reinstall option must be used when using the Reset this PC feature.
 * At the time of release, the update process had a chance of hanging for extended periods of time when attempting to install this build.
 * At the time of this build's release, some Windows Insiders were unable to update to this build and instead got an error with the error code 0x8007042b.
 * When certain external USB 3.0 drives are attached, they stop responding with Start Code 10.
 * Drive Optimizer incorrectly reports that optimization was never run on some devices.
 * The documents section in the privacy settings has a broken icon, and as such, a rectangle shows in its place.
 * Remote Desktop Connection crashes when attempting to connect to multiple sessions.
 * Snipping does not work on secondary monitors.
 * The IME candidate window for the East Asian IMEs (like the Simplified Chinese, Traditional Chinese, and the Japanese IMEs) sometimes does not open. If this bug is encountered, change the focus to another application or text field and back to the area that was being originally worked on. Ending the process  via Task Manager can also workaround this bug as well.