This update includes a plethora of fixes for the Windows 11 22H2 OS which will likely be released in the next few months. It also includes improvements to over 200 Canadian Syllabic characters. Moreover, some changes have been made for the IT administrators which you ought to take into consideration if you are a sysadmin. Let us discuss these improvements in detail, and then continue to learn how to install this build.

New in Windows 11 Build 25140

Improvements to Canadian Syllabic Characters

The font for the various Canadian Syllabic characters has been improved which are used by most Euphemia typefaces, including Cree orthographies, Inuktitut, and the Carrier/Dakelh script (dulkw’ahke). The fonts of 200 characters have been updated to improve the legibility and screen rendering. Moreover, new glyphs have also been added to support Unicode 14 characters for the Nattilik language of the Canadian arctic.Examples of new glyphs in the Euphemia typeface. Source: Microsoft

Changes for IT Admins

As we mentioned earlier, some changes to the OS policies have been announced with this flight. However, the changes will be implemented with an update to the Dev channel in the future. Microsoft intimates the end-users that the devices with the diagnostics data turned on and are joined to an Azure Active Directory (AAD) tenant with a billing address in the EU or EFTA, will be enrolled in the Windows diagnostic data processor configuration. After installing build 25140, the following conditions are applied to the Dev channel devices that are joined to an Azure AD tenant with a billing address outside of the EU or EFTA:

Devices can’t be enabled for the Windows diagnostic data processor configuration at this time.The processor configuration will be disabled in any devices that were previously enabled.Microsoft will act as the controller for Windows diagnostic data in accordance with the Microsoft Privacy Statement and the Data Protection Addendum terms won’t apply.

With these conditions, Microsoft suggests that the users pause receiving insider flights if these are not acceptable:

Other Improvements and Fixes

Other changes and fixes have also been made with this flight:

[File Explorer]An issue that was leading some people to unexpectedly see the error 0x80070026 when copying files from network drives has been fixed.An issue where the active tab color didn’t match the command bar below it has been addressed.An issue where dragging to rearrange tabs wasn’t working has been fixed.An issue that could cause artifacts in the windows thumbnail preview in the taskbar if File Explorer was maximized and you used the Windows Key + M shortcut keys to minimize it, has been taken care of.[Settings]If you go to rename a drive label in the Settings app » System » Storage » Disks & Volumes, the current drive name will now be prepopulated in the dialog.[Input]An issue where selecting English (New Zealand) in the Out of Box Experience (OOBE) was unexpectedly leading to the Arabic (101) keyboard getting selected has been fixed.Setting language bar hotkeys for switching input directly to a specific non-IME input method should work now.The issue of some settings such as new user account locale, Input (Keyboard), and UPLL (User Preferred Language List) was not getting updated when an admin user tried to install a speech recognition language. This issue has now been fixed.An issue causing Batang, BatangChe, Gungsuh, and GungsuhChe fonts to not render Korean correctly when using Office online apps when these fonts were not locally present on your PC has been fixed.[Task Manager]A crash that could happen when switching modes on pages other than the Processes page has been fixed.A small adjustment has been made to the intensity of the colors used in the heatmap on the Processes page.[Other]An issue where calls to CopyAccelaratorTable and CreateAcceleratorTable would fail of the LPACCEL parameter was the address of an odd-numbered index into an array of ACCEL structs has been fixed.An issue with x64 emulation on ARM64 devices that could result in certain apps crashing on launch with error code 0xc0000409 has been addressed.An issue causing the audio to stop playing in certain apps after a minute has been fixed.

With these new features, improvements, and fixes, there are also a few known issues we think you should know about before upgrading to this build.

Known Issues

[General]Windows Insiders on Surface Pro X devices will hit a black screen when attempting to resume from hibernate on this build. To mitigate this problem, you must power cycle (long power button shutdown) to get back into the device. If this becomes a nuisance, you can roll back to the previous OS build or disable hibernation mode.There are reports that the Mica material and Acrylic blur effect is not rendering correctly in OS surfaces like the Start menu, Notification Center and other areas.There are reports that shutting down via the Start menu isn’t working for some Insiders and is unexpectedly rebooting instead.Some games that use Easy Anti-Cheat may crash or cause your PC to bugcheck.[File Explorer]The up arrow is misaligned in the File Explorer tabs. This will be fixed in a future update.There are reports that launching the File Explorer in certain ways when using the dark mode (for example, from the command line) is showing the body of File Explorer unexpectedly in light mode.[Widgets]An issue causing the Widgets preferences (temperature units and pinned widgets) to unexpectedly reset to default is being investigated.[Live captions]Certain apps in full screen (e.g., video players) prevent live captions from being visible.Certain apps positioned near the top of the screen and closed before live captions is run will re-launch behind the live captions window positioned at the top. Use the system menu (ALT + Spacebar) while the app has focus to move the app’s window further down.

Some of these issues have prolonged over the last few flights in the Dev channel, but some of them are new with this flight. Hopefully, Microsoft will address these in future releases.

Download and Install Windows 11 Build 25140

To install this update, you either need to be running Windows 11 and subscribed to the Dev channel, or perform a clean install using the ISO image provided by Microsoft.

Windows Update

If you have enabled Windows updates, you will automatically get a “New features are ready to install” prompt. Follow the steps below to upgrade to this build: Once the computer restarts, you can verify that the OS has been updated by typing in winver in the Run Command box.Windows 11 Dev channel updated Click Download and install in front of it.Download and install the update

Download Windows 11 Build 25140 ISO Image

You can also download the ISO image for Windows 11 Build 25140 and perform a clean install. Here is how: You are now set to perform a fresh installation of Windows 11 Dev Build 25140 using the downloaded ISO image. Learn how to create a multiboot USB installation media using Ventoy.

Rollback/Remove Windows 11 Insider Preview Update

If you do not wish to keep the installed preview update for some reason, you can always roll back to the previous build of the OS. However, this can only be performed within the next 10 days after installing the new update. To roll back after 10 days, you will need to apply this trick.

Cleanup After Installing Windows Updates

If you want to save space after installing Windows updates, you can run the following commands one after the other in Command Prompt with administrative privileges: Also see:

Windows 11 Build 25151 With Redesigned “Open With” Dialog BoxDownload Windows 11 Build 25179 ISO Image With FixesWindows 11 Build 25169 Released With App LockdownWindows 11 Build 22621 Released To Beta Channel: Potential 22H2 ReleaseWindows 11 Build 25136 Brings File Explorer Tabs, Notepad & Media Player Enhancements