Microsoft Windows 10 20H2 insider 19559.1000. rs_prerelease.200131-1437

Good morning, friends! Microsoft has released a new pre-build of Windows 10, numbered 19559, for members of the Windows Insider program who use the “early access” channel (Fast Ring).

Full build number: 19559.1000. rs_prerelease.200131-1437.

We remind you that the “Early access” channel releases build that may contain rather unpleasant errors. If you need more stability, we recommend switching to the Slow (Late access) or Release Preview channels.

Bug fixes and improvements

• Fixed an issue where the offer window for East Asian IMES (simplified Chinese, traditional Chinese, and Japanese IMES) might not open on previous builds.
• Fixed an issue that could cause explorer to crash.exe when backing up folders containing files .heic or RAW.
• Fixed an issue that could cause explorer to crash.exe when trying to delete some large ones .tif files.
• Fixed an issue where several upper window pixels were cropped when using THE win + combination and then snapping the window to the right or left border using WIN + or WIN + .
• Fixed an issue that caused the event Viewer tool to crash when selecting certain recent events.
• Now insiders using an ARM64-based device, such as Surface Pro X, can install Hyper-V if the device uses a Pro or Enterprise edition system.
• Fixed an issue that caused some insiders to get a GSOD with the KMODE EXCEPTION NOT HANDLED error on previous builds.

Known error

• BattlEye and Microsoft have identified issues with the compatibility of some Insider Preview builds with certain versions of the anti-cheat program BattlEye due to changes in the operating system. To protect insiders who may have these versions installed, a restriction has been implemented so that Insider Preview builds will not be offered for devices that may be affected by this issue. More information can be found here.
• Microsoft is aware of a problem with Screen announcer and NVDA users using the new version of Microsoft Edge based on Chromium, which may cause some difficulties when navigating and reading certain web content. Development teams are working to fix the problem. The problem does not affect users of an outdated version of Microsoft Edge.
• We investigate reports that the system update process may hang for a long time when trying to install a new build.
• We are investigating reports that some insiders cannot update to new builds due to the 0×8007042b error.
• We are investigating reports that some insiders cannot update to new builds due to the 0xc1900101 error.
• East Asian IMES (simplified Chinese, traditional Chinese, Korean, and Japanese IMES) may not be available in the language switching menu and when using keyboard shortcuts to change the language (for example, WIN + ) after upgrading from build 19041 (20H1) or earlier to insider builds of Windows 10 (build 19536 or later) if multiple languages or keyboard layouts have been added. Microsoft is investigating the problem. In the meantime, you can delete and re-add all keyboard layouts that are not currently available in the language switching menu. This issue will not occur if you are upgrading from build 19536 or later.
• The “Documents” section in the privacy settings does not display an icon correctly (a simple rectangle).
• We are investigating reports that some devices cannot go to sleep mode if they are idle for a certain time. Microsoft has identified the root cause of the problem and is working on a fix that should be included in the next build. If the problem affects your device, you can use the manual transition to sleep mode, which should work correctly (“start” – > power button – > “Sleep mode”).
• WSL Issue 4860: some insiders have an error message when using WSL2: “connection Attempt failed”. Microsoft thanks insiders who reported the problem. The fix is ready and will be included in the next build.
• In this build, there is a problem that when you open and then close the clipboard history (WIN + V) without inserting elements, input stops working in many places in the system. The problem is solved by restarting the device. Microsoft thanks you for your patience.