Windows 10 Build 19559 Start Push: ARM64 Device SPSupport Hyper-V

This morning (February 6), Microsoft pushed a new preview of the version of Build 19559.1000 for Windows 10 Fast Track users. Disappointingly, this update doesn’t feature significant new features, and it’s probably worth saying that ARM64 devices (such as Surface Pro X) can also enable Hyper-V virtualization, but only if you need to run SKUs like Windows 10 Pro/Enterprise.

Windows 10 Build 19559 Start Push: ARM64 Device SPSupport Hyper-V

Bug repair aspects of the content are mainly, in some cases, simple, traditional, Japanese input method does not display candidate boxes, exit the folder containing .heic or RAW files, the resource manager crashes, delete some .tif files when the resource manager hangs, Win-plus arrow key move the window, the loss of pixels Event Viewer crashes and some Insider members experience issues such as the green screen that displays “KMODE EXCEPTION NOT HANDLED” errors.

Of course, as always, this version still has some problems that have been found but have not yet been able to solve, such as 0x8007042b/0xc1900101 error can not be updated, add a simple / Traditional Chinese / Korean / Japanese and other multi-language input method after the loss of some keyboards.

Full update list:

We fixed an issue with the IME candidate window for East Asian IMEs (Simplified Chinese, Traditional Chinese, and the Japa Nese IME) not open ters on recent builds.

We fixed an an a can-be can-be in explorer.exe crashing out out of the folders.heic or RAW files.

We fixed an it can can can be in explorer.exe hanging attempt sings to delete certain .large tif files.

We fixed an an sings an sings ing in the top pixels of a window getting the clipped when using the use WIN and then then then ing the window to the side using WIN and Left/Right.

We fixed an saly sing in event viewer sidrin sieve sieve sieve siad yn events.

For any of the insiders using an arm64 device, such as the Surface Pro X, running Enterprise or Pro edition, you’ll now be able to see and Hyper-V features.

We fixed an an san saly sings in insiders sifing a green screen in-post builds with error KMODE EXCEPTION NOT H ANDLED.

Fixed issues:

BattlEye and Microsoft have had found incompatibility issues due to changes in the operating system system to some insider Si ew builds and certain s of certains of BattlEye anti-cheat software. To safeguard insiders who had have these version s installed on PC theirs, we have applied ed a compatibility hold on these ddd evices from the right to offer ed affected builds of Windows Insider Preview. See this article for details.

We are aware narrator and NVDA that-there sifind sit-out-of-the-go release of Microsoft Edge build on Chromium may experience some Yny when navigating and a certain reading web content. Narrator, NVDA, and the Edge teams are aware of these issues. Users of legacy Microsoft Edge will not be affected.

We’re looking into reports of the update process hanging for extended ters of time when attempting to install a new bui Ld.

We’re the insider reports insiders are unable to update to newer builds with error 0x8007042b.

We’re looking into reports that insiders are unable to update to newer builds with error 0xc1900101.

East Asian IMEs (Simplified Chinese, General Chinese, Korean and Japanese IME) may be missing from the language/keyboard switcher (e.g. opened by Windows key and Space key) after upgradeing from 20H1 Build 19041 or lower builds to Windows 10 Preview Insider build (19536 or later) if you have had multiple languages/keyboards added. We are the siar ing the issue. In the meantime, the remove and remove and the re-add any keyboards that are the missing from the keyboard switcher by-time to settings and time and Language sgt; Language sgted languages. It doesn’t’t happen if you updated from build19536 or later.

The Documents section under Privacy has a broken icon (just a rectangle).

We’re sing reports that certain devices are no longer sleeping on idle. We have ed d’eted the root cause and are working on a fix for an upcoming flight. If your device is impacted, manually triggering sleep should work (Start and Power button and Sleep).

WSLS Is are experiencing this message message when using WSL2: A connection failed on Windows. Thank you if you have one of those who reported it on the previous flight-we have a fix ready will will bein An upcoming flight.

There’s an issue in this build where if you bring up the clipboard history (WIN-v) and the dismiss it pastout pasting anything, in Put in many places will stop working until you reboot your PC. We appreciate your patience.