Announcing Windows 11 Insider Preview Build 25314

  • Thread starter Brandon LeBlanc
  • Start date
Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 25314 to the Canary Channel. As a reminder, Windows Insiders who were previously in the Dev Channel on 25000 series builds are being moved to the new Canary Channel. This migration continues to happen in the background, but if you are on Build 25309 and haven’t been moved to the Canary Channel yet, you can either wait to be moved or move yourself to the Canary Channel on your own via Settings > Windows Update > Windows Insider Program to receive Build 25314 today. If you would like to move back to the Dev Channel, you can follow these instructions to do a clean installation of Windows 11 and then re-join the Dev Channel to receive 23000 series builds in this channel going forward. As builds released to the Canary Channel are “hot off the presses,” we will offer limited documentation for builds flighted to the Canary Channel (no known issues for example), but we will not publish a blog post for every flight – only when new features are available in a build.

What’s new in Build 25314

Access Keys in File Explorer

We are adding access key shortcuts into the XAML context menu in File Explorer. An access key is a one keystroke shortcut that allows a keyboard user to quickly execute a command in context menu. Each access key will correspond with a letter in the display name. It's part of our effort to make File Explorer more accessible. To try this out, you can click on a file in File Explorer and press the menu key on your keyboard. NOTE: If you see the “pizza” icon on the command bar in File Explorer that denotes you are previewing the Windows App SDK version of File Explorer, you will not see this feature yet. [caption id="attachment_176116" align="alignnone" width="427"]fe-access-keys.png Access keys in the XAML context menu in File Explorer.[/caption] [We are beginning to roll this out, so the experience isn’t available to all Insiders in the Canary Channel just yet as we plan to monitor feedback and see how it lands before pushing it out to everyone.] FEEDBACK: Please file feedback in Feedback Hub (WIN + F) under Files, Folders, and Online Storage > File Explorer.

File Recommendations in File Explorer

File Recommendations are coming to File Explorer Home to bring users the most relevant file content right to their fingertips. This feature (as pictured below) will be available to users signed into Windows with an Azure Active Directory (AAD) account. Files that are recommended will be cloud files associated with that account, either owned by the user, or shared with the user. [caption id="attachment_176117" align="alignnone" width="732"]fe-recommended-files-2-1024x663.png File recommendations in File Explorer for users signed in with an AAD account.[/caption] [We are beginning to roll this out, so the experience isn’t available to all Insiders in the Canary Channel just yet as we plan to monitor feedback and see how it lands before pushing it out to everyone.] FEEDBACK: Please file feedback in Feedback Hub (WIN + F) under Files, Folders, and Online Storage > File Explorer.

Introducing LSA Protection Enablement on Upgrade

Local Security Authority (LSA) protection helps protect against theft of secrets and credentials used for logon by preventing unauthorized code from running in the LSA process and by preventing dumping of process memory. Starting with on upgrade, we will audit for a period of time to check for incompatibilities with LSA protection. If we do not detect any incompatibilities, we will automatically turn on LSA Protection. You can check and change the enablement state of LSA protection in the Windows Security application under the Device Security > Core Isolation page. [caption id="attachment_176121" align="alignnone" width="668"]lsa-on-upgrade-1024x743.png Local Security Authority (LSA) protection in Windows Security.[/caption] LSA protection records whether programs are blocked from loading into LSA in the event log. If you would like to check if something has been blocked, information on the logs recorded is available here. Feedback: Please file feedback in Feedback Hub (WIN+F) under Security and Privacy > Logging Into Your PC.

Narrator Outlook Support

Narrator will now retrieve updates to its Outlook support when Narrator is started. You can learn more about the work we did for Outlook in Chapter 5 of the Narrator User Guide. We have not added any additional functionality to our Outlook support, but this work will allow updates to the Outlook experience to be made through the Microsoft Store. You will receive a notification after the download is completed to inform you that the update has been retrieved. With this change, Narrator’s Outlook support is limited to U.S. English only. Other languages will be supported in a future flight. FEEDBACK: Please file feedback in Feedback Hub (WIN + F) under Accessibility > Narrator.

Changes and Improvements

[General]

To increase security in Windows 11, starting with this build and later we are disabling the Remote Mailslot Protocol by default. The legacy Remote Mailslot Protocol is a simple, unreliable, insecure, and unidirectional inter-process communications protocol between a client and server and was introduced in Windows NT 3.1 and will be deprecated in a future Windows release. If an application attempts to open a Remote Mailslot session over the SMB protocol, you may see one or more of the following errors:
  • 3025 ERROR_REMOTE_MAILSLOTS_DEPRECATED
  • “The requested operation failed. Remote mailslots have been deprecated.”
If your application still uses Remote Mailslot, contact your vendor about updating their software. The legacy Remote Mailslot is not secure and should not be used under any circumstances. If you need to temporarily enable Remote Mailslot, run the following command in an elevated PowerShell console:
PS C:\> Set-SmbClientConfiguration -EnableMailslots $true

About the Canary Channel

The Canary Channel is the place to preview platform changes that require longer-lead time before getting released to customers. Some examples of this include major changes to the Windows kernel, new APIs, etc. Builds that we release to the Canary Channel should not be seen as matched to any specific release of Windows and some of the changes we try out in the Canary Channel will never ship, and others could show up in future Windows releases when they’re ready. The builds that will be flighted to the Canary Channel will be “hot off the presses,” flighting very soon after they are built, which means very little validation and documentation will be done before they are offered to Insiders. These builds could include major issues that could result in not being able to use your PC correctly or even in some rare cases require you to reinstall Windows. We will offer limited documentation for the Canary Channel, but we will not publish a blog post for every flight – only when new features are available in a build. Our Canary Channel won’t receive daily builds; however, we may ramp up releasing builds more frequently in the future. The desktop watermark you see at the lower right corner of your desktop is normal for these pre-release builds.

Important Insider Links

Thanks, Amanda & Brandon

Continue reading...
 

Similar threads

A
Replies
0
Views
18
Amanda Langowski
A
A
Replies
0
Views
27
Amanda Langowski
A
A
Replies
0
Views
16
Amanda Langowski
A
A
Replies
0
Views
31
Amanda Langowski
A
A
Replies
0
Views
48
Amanda Langowski
A
Back
Top Bottom