Windows 10 build 19551.1005

10.0.19551.1005.rs_prerelease_flt.200118-2110
Build of Manganese
10.0.19551.1005.rs_prerelease_flt.200118-2110
OS family
Architecturex86, x64, ARM64
Compiled2020-01-18
Timebomb2020-07-31 (+195 days)
Works in
About
Win10-19551-1005winver.png
SKUs
Home (N, Single Language, China)
Pro (N, Single Language, China)
Pro Education (N)
Pro for Workstations (N)
Education (N)
Enterprise (G, N)
Enterprise Evaluation (N)
Enterprise multi-session
IoT Enterprise
Team
Key
Use a Windows 10 Retail serial
TCB.png

Windows 10 build 19551.1005 is the fourth Insider Preview build of Manganese, the 20H2 development semester of Windows as a service. This build was released to Windows Insiders in the Fast Ring on 23 January 2020 and has general changes, improvements, and bug fixes which are listed in the official release announcement.

Bugs and quirks[edit | edit source]

  • You must use an IDE or SATA hard drive if you want to install this build in VMware Workstation, 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.
  • The update process to this build has a chance of hanging for extended periods of time.
  • At the time of this build's release, some Windows Insiders were unable to update to this build and instead got an error with either the error codes 0x8007042b or 0xc1900101.
  • When certain external USB 3.0 drives are attached, they stop responding with Start Code 10.
  • The documents section in the privacy settings has a broken icon, and as such, a rectangle shows in its place.
  • 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 TextInputHost.exe via Task Manager can also workaround this bug as well.
  • At the time of the build's release, there was a bug that prevented ARM64 devices from updating to this build successfully.

Gallery[edit | edit source]

External links[edit | edit source]