Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 25140 to the Dev Channel.
We are releasing ISOs for this build – they can be downloaded here.
This build includes another good set of fixes that improve the overall experience for Windows Insiders on the latest preview builds.
Changes and Improvements
Euphemia typeface covers most languages that use the Canadian Syllabic script including various Cree orthographies, Inuktitut, and the Carrier/Dakelh script (dulkw’ahke). In the latest Insider builds, we’ve updated this font to improve the legibility and screen rendering of over 200 characters at various sizes. We’ve also added new glyphs to support Unicode 14 characters for the Nattilik language of the Canadian arctic.Example of some of the new glyphs in the Euphemia typeface.
Fixed an issue which was leading some people to unexpectedly see error 0x80070026 when copying files from network drives.
Fixed an issue where the active tab color didn’t match the command bar below it.
Fixed an issue where dragging to rearrange tabs wasn’t working sometimes.
Fixed an issue which could cause artifacts in the windows thumbnail preview in the taskbar if File Explorer was maximized and you used WIN + M to minimize it.
If you go to rename a drive label in System > Storage > Disks & Volumes, the current drive name will now be prepopulated in the dialog.
Fixed an issue where selecting English (New Zealand) in OOBE was unexpectedly leading to the Arabic (101) keyboard getting selected.
Setting language bar hotkeys for switching input directly to specific non-IME input method should work now.
Some languages don’t support text-to-speech. When an admin user tried to install one of those languages using the new Install-Language CopyToSettings command, some settings such as new user account locale, Input (Keyboard), and UPLL (User Preferred Language List) were not getting updated. This issue has now been fixed.
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.
Fixed a crash that could happen when switching modes in pages other than the Processes page.
We made a small adjustment to the intensity of the colors used in the heatmap on the Processes page.
Fixed an issue where calls to CopyAcceleratorTable and CreateAcceleratorTable would fail if the LPACCEL parameter was the address of an odd numbered index into an array of ACCEL structs.
Fixed an issue with x64 emulation on ARM64 which could result in certain apps crashing on launch with error code 0xc0000409.
Fixed an issue causing audio to stop playing in certain apps after a minute.
NOTE: Some fixes noted here in Insider Preview builds from the Dev Channel may make their way into the servicing updates for the released version of Windows 11.
Windows Insiders on Surface Pro X devices will hit a black screen attempting to resume from hibernate on this build. You will need to power cycle (long power button shutdown) to get back into the device. It is recommended Insiders on these devices pause flighting until we release a build with this fix.
We are investigating reports that the Mica material and Acrylic blur effect is not rendering correct in OS surfaces like the Start menu, Notification Center and other areas.
We’re investigating 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.
The up arrow is misaligned in File Explorer tabs. This will be fixed in a future update.
[NEW] We’re investigating reports that launching File Explorer in certain ways when using dark mode (for example, from the command line) is showing the body of File Explorer unexpectedly in light mode.
[NEW] We’re working on the fix for an issue causing Widgets preferences (temperature units and pinned widgets) to unexpectedly reset to default.
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 top. Use the system menu (ALT + Spacebar) while the app has focus to move the app’s window further down.
Changes for IT administrators
We’re making changes to how IT admins enroll devices in the Windows diagnostic data processor configuration option. In a future Insider Preview build in the Dev Channel, devices with diagnostic data turned on and joined to an AAD tenant with billing address in the EU or EFTA, will be enrolled in the Windows diagnostic data processor configuration. During this initial rollout, the following conditions apply to devices in the Dev Channel 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 Addendumterms won’t apply.
It’s recommended Insiders on these devices pause flighting if these changes aren’t acceptable. Learn more at https://aka.ms/configwddenterprise.
You can download the latest Windows Insider SDK at aka.ms/windowsinsidersdk.
SDK NuGet packages are now also flighting at NuGet Gallery | WindowsSDK which include:
.NET TFM packages for use in .NET apps as described at ms/windowsinsidersdk
C++ packages for Win32 headers and libs per architecture
BuildTools package when you just need tools like MakeAppx.exe, MakePri.exe, and SignTool.exe
These NuGet packages provide more granular access to the SDK and better integrate in CI/CD pipelines.
About the Dev Channel [UPDATED]
The Dev Channel receives builds that represent long lead work from our engineers with features and experiences that may never get released as we try out different concepts and get feedback. It is important to remember that the builds we release to the Dev Channel should not be seen as matched to any specific release of Windows and the features included may change over time, be removed, or replaced in Insider builds or may never be released beyond Windows Insiders to general customers. For more information, please read this blog post about how we plan to use the Dev Channel to incubate new ideas, work on long lead items, and control the states of individual features.
These aren’t always stable builds, and sometimes you will see issues that block key activities or require workarounds. It is important to make sure you read the known issues listed in our blog posts as we document many of these issues with each flight.
Build numbers are higher in the Dev Channel than the Windows 11 preview builds in the Beta and Release Preview Channels. You will not be able to switch from the Dev Channel to the Beta or Release Preview Channels without doing a clean install back to the released version of Windows 11 currently.
ALSO: Because the Dev and Beta Channels represent parallel development paths from our engineers, there may be cases where features and experiences show up in the Beta Channel first.
The desktop watermark you see at the lower right corner of your desktop is normal for these pre-release builds.
Important Insider Links
Want to learn how we made Windows 11? Check out our Inside Windows 11 website to hear and meet our makers from Engineering, Design and Research to share their insights and unique perspectives throughout this journey.
You can check out our Windows Insider Program documentation here.
Check out Flight Hub for a complete look at what build is in which Insider channel.
Amanda & Brandon