Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 26212 to the Canary Channel.

Developers, please note that for a short period of time, we will not be releasing an SDK for builds we flight to the Canary Channel.

Changes and Improvements

[Windows Share]

• Users will be able to now generate QR codes for URLs and cloud file links through the Windows share window to seamlessly share webpages and files across their devices. To try this out in Microsoft Edge, just click the share button in the Edge toolbar and choose “Windows share options”.

• To prevent accidentally closing the Windows share window, clicking outside the Windows share window will no longer close it. To close the Windows share window, just press the close button at the top right corner.
• If your Microsoft account uses a Gmail address, you can now send email to yourself from Windows share window and receive it in your Gmail account.

[Copilot in Windows*]

• Over the last few months, we’ve been trying out different experiences for Copilot in Windows (Preview) with Windows Insiders across the Canary, Dev, and Beta Channels. Some of these experiences include the ability for Copilot in Windows to act like a normal application window and the taskbar icon animating to indicate that Copilot can help when you copy text or images. We have decided to pause the rollouts of these experiences to further refine them based on user feedback. Copilot in Windows will continue to work as expected while we continue to evolve new ideas with Windows Insiders.

Fixes for known issues

[General]

• We fixed the issue causing advanced startup options to not work. This also fixes the progress wheel from not showing when booting.
• We believe we fixed the issue causing Features on Demand (FODs) to not install.

[Copilot in Windows*]

• We are rolling out a fix for the issue causing Copilot to auto-launch unexpectedly for Windows Insiders in the Canary, Dev, and Beta Channels after restarting their PCs. This issue was unrelated to the auto-launching experience we tried out with Insiders in the Canary and Dev Channels in early Februarywhich we stopped rolling out in March.

[Taskbar & System Tray]

• Fixed an issue that caused the taskbar to be partially off the screen on secondary monitors.
• Fixed an issue that caused Narrator to be silent while rearranging your apps on taskbar.

[File Explorer]

• Fixed an issue which was causing File Explorer to sporadically crash when using path suggestions in the address bar.
• Fixed an issue which could cause File Explorer to crash sometimes when going from the search box to the body of File Explorer.

[Windowing]

• Fixed a couple DWM crashes, which could cause the screen to appear to flash.

[Other]

• Fixed an issue that was causing some people to repeatedly see a message saying live captions were being missed.
• Fixed an underlying issue which was causing Visual Studio to fail to debug x64 .NET framework console applications (the app would crash in ntdll.dll upon load).

Known issues

[General]

• [IMPORTANT NOTE] We are investigating reports that some Windows Insiders in the Canary and Dev Channels are stuck on Build 26040 or Build 23620. The investigation is ongoing, however if you are impacted by this and really want to get onto the latest build in the Canary or Dev Channel today – you can download the latest ISO here and do a clean install and opt your device back into flighting in the Canary or Dev Channels.

Reminders for Windows Insiders in the Canary Channel

• The builds we release to the Canary Channel should not be seen as matched to any specific release of Windows and features and experiences included in these builds may never get released as we try out different concepts and get feedback. Features may change over time, be removed, or replaced and never get released beyond Windows Insiders. Some of these features and experiences could show up in future Windows releases when they’re ready.
• Many features in the Canary Channel are rolled out using Control Feature Rollout technology, starting with a subset of Insiders and ramping up over time as we monitor feedback to see how they land before pushing them out to everyone in this channel.
• To get off the Canary Channel, a clean install of Windows 11 will be required. As a reminder – Insiders can’t switch to a channel that is receiving builds with lower build numbers without doing a clean installation of Windows 11 due to technical setup requirements.

• The desktop watermark shown at the lower right corner of the desktop is normal for these pre-release builds.

• Check out Flight Hub for a complete look at what build is in which Insider channel.

• Copilot in Windows* in preview is being rolled out gradually to Windows Insiders in select global markets. The initial markets for the Copilot in Windows preview include North America, United Kingdom and parts of Asia and South America. It is our intention to add additional markets over time.

Thanks,
Amanda & Brandon

Source: Windows Blog
—

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 26120.461 (KB5037009) to the Dev Channel.

Windows Insiders in the Dev Channel will now receive updates based on Windows 11, version 24H2 via an enablement package (Build 26120.xxxx). For Insiders in the Dev Channel who want to be the first to get features gradually rolled out to you, you can turn ON the toggle (shown in the image below) to get the latest updates as they are available via Settings > Windows Update. Over time, we will increase the rollouts of features to everyone with the toggle turned on. Should you keep this toggle off, new features will gradually be rolled out to your device over time once they are ready.

Going forward, we will document changes in Dev Channel builds in two buckets: new features, improvements, and fixes that are being gradually rolled out for Insiders who have turned on the toggle to get the latest updates as they are available and then new features, improvements, and fixes available to everyone in the Dev Channel.

Changes and Improvements gradually being rolled out to the Dev Channel with toggle on*

[General]

• This update includes a small set of general improvements and fixes that improve the overall experience for Insiders running this build on their PCs.

Changes and Improvements gradually being rolled out to everyone in the Dev Channel

[Copilot in Windows**]

• Over the last few months, we’ve been trying out different experiences for Copilot in Windows (Preview) with Windows Insiders across the Canary, Dev, and Beta Channels. Some of these experiences include the ability for Copilot in Windows to act like a normal application window and the taskbar icon animating to indicate that Copilot can help when you copy text or images. We have decided to pause the rollouts of these experiences to further refine them based on user feedback. Copilot in Windows will continue to work as expected while we continue to evolve new ideas with Windows Insiders.

Fixes for everyone in the Dev Channel

[Copilot in Windows**]

• We are rolling out a fix for the issue causing Copilot to auto-launch unexpectedly for Windows Insiders in the Canary, Dev, and Beta Channels after restarting their PCs. This issue was unrelated to the auto-launching experience we tried out with Insiders in the Canary and Dev Channels in early February which we stopped rolling out in March.

Reminders for Windows Insiders in the Dev Channel

• Updates released to the Dev Channel are based off Windows 11, version 24H2.
• Features and experiences included in these builds may never get released as we try out different concepts and get feedback. Features may change over time, be removed, or replaced and never get released beyond Windows Insiders. Some of these features and experiences could show up in future Windows releases when they’re ready.
• Many features in the Dev Channel are rolled out using Control Feature Rollout technology, starting with a subset of Insiders and ramping up over time as we monitor feedback to see how they land before pushing them out to everyone in this channel.
• Windows Insiders in the Dev Channel who want to be the first to get features gradually rolled out to you*, you can turn ON the toggle to get the latest updates as they are available via Settings > Windows Update. Over time, we will increase the rollouts of features to everyone with the toggle turned on. Should you keep this toggle off, new features will gradually be rolled out to your device over time once they are ready.
• 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.
• Check out Flight Hub for a complete look at what build is in which Insider channel.
• Copilot in Windows** in preview is being rolled out gradually to Windows Insiders in select global markets. The initial markets for the Copilot in Windows preview include North America, United Kingdom and parts of Asia and South America. It is our intention to add additional markets over time.

Thanks,
Amanda & Brandon

Source: Windows Blog
—

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 22635.3570 (KB5037008) to the Beta Channel.

REMINDER: All Windows Insiders in the Beta Channel will now be on the same build (Build 22635.xxxx) via an enablement package. For Windows Insiders in the Beta Channel who want to be the first to get features gradually rolled out to you, you can turn ON the toggle (shown in the image below) to get the latest updates as they are available via Settings > Windows Update. Over time, we will increase the rollouts of features to everyone with the toggle turned on. Should you keep this toggle off, new features will gradually be rolled out to your device over time once they are ready.

Going forward, we will document changes in Beta Channel builds in two buckets: new features, improvements, and fixes that are being gradually rolled out for Insiders who have turned on the toggle to get the latest updates as they are available and then new features, improvements, and fixes available to everyone in the Beta Channel.

Changes and Improvements gradually being rolled out to the Beta Channel with toggle on*

[File Explorer] 

• We’re rolling out the ability to duplicate a tab by right-clicking on a tab in File Explorer.

Fixes gradually being rolled out to the Beta Channel with toggle on*

[File Explorer]

• Fixed a memory leak when interacting with archive folders in File Explorer.
• Fixed a few issues impacting File Explorer reliability.
• Made a change to help fix an issue which could cause the spacing between your desktop icons to become extremely wide.
• Fixed a timing issue where if you start a search from Home in File Explorer, it may unexpectedly show no results the first time you tried.
• Did some work to help address an issue where the address bar dropdown might appear unexpectedly while you were using File Explorer.

[Task Manager]

• Updated the units (from MHz to MT/s) for DDR speed.
• Fixed an issue where the Safely Remove Hardware option for ejecting USB devices wouldn’t work if Task Manager was open.
• Did some work to ensure Task Manager releases process handles quickly when terminating processes.
• Made some more improvements to help with Task Manager reliability.
• We have improved the performance when changing the sort order.
• Made multiple improvements to overall accessibility of Task Manager, including improving keyboard focus, tab navigation, text scaling, names of items read out by screen readers, and more.
• We made it a little easier to resize Task Manager when trying to resize by grabbing the top of the window.

Changes and Improvements gradually being rolled out to everyone in the Beta Channel

[Copilot in Windows**]

• Over the last few months, we’ve been trying out different experiences for Copilot in Windows (Preview) with Windows Insiders across the Canary, Dev, and Beta Channels. Some of these experiences include the ability for Copilot in Windows to act like a normal application window and the taskbar icon animating to indicate that Copilot can help when you copy text or images. We have decided to pause the rollouts of these experiences to further refine them based on user feedback. Copilot in Windows will continue to work as expected while we continue to evolve new ideas with Windows Insiders.

Fixes for everyone in the Beta Channel

[Start menu]

• We fixed the issue causing a component related to upgrading and restoring data from Windows Backup called “Global.WindowsMigration” to incorrectly show under the Start menu > All apps.

[Copilot in Windows**]

• We are rolling out a fix for the issue causing Copilot to auto-launch unexpectedly for Windows Insiders in the Canary, Dev, and Beta Channels after restarting their PCs. This issue was unrelated to the auto-launching experience we tried out with Insiders in the Canary and Dev Channels in early February which we stopped rolling out in March.

Known issues

[General]

• We are investigating an issue where Internet Information Services (IIS) and Windows Communication Foundation (WCF) may not work after installing this update.

[Widgets]

Windows Insiders in the Beta Channel who have the new position for the Widgets entry-point on left-aligned taskbars may see the following known issues:

• Swipe invocation for Widgets may not work if taskbar is center-aligned instead of left-aligned.
• Unpinning Widgets from the taskbar may not work if taskbar is center-aligned instead of left-aligned.
• The Widgets board is incorrectly positioned when Copilot is in side-by-side mode.
• Turning on/off Widgets in taskbar settings may refresh the taskbar.

Reminders for Windows Insiders in the Beta Channel

• Updates released to the Beta Channel are based off Windows 11, version 23H2.
• Features and experiences included in these builds may never get released as we try out different concepts and get feedback. Features may change over time, be removed, or replaced and never get released beyond Windows Insiders. Some of these features and experiences could show up in future Windows releases when they’re ready.
• Many features in the Beta Channel are rolled out using Control Feature Rollout technology, starting with a subset of Insiders and ramping up over time as we monitor feedback to see how they land before pushing them out to everyone in this channel.
• Windows Insiders in the Beta Channel who want to be the first to get features gradually rolled out to you*, you can turn ON the toggle to get the latest updates as they are available via Settings > Windows Update. Over time, we will increase the rollouts of features to everyone with the toggle turned on. Should you keep this toggle off, new features will gradually be rolled out to your device over time once they are ready.
• 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.
• Check out Flight Hub for a complete look at what build is in which Insider channel.
• Copilot in Windows** in preview is being rolled out gradually to Windows Insiders in select global markets. The initial markets for the Copilot in Windows preview include North America, United Kingdom and parts of Asia and South America. It is our intention to add additional markets over time.

Thanks,
Amanda & Brandon

Source: Windows Blog
—

Boost your gaming experience even more with the new resource controls setting in Microsoft Edge 125!

Thanks to efficiency mode, Edge already reduces how much of your computer resources the browser uses while you play PC games. And now, starting with Microsoft Edge Beta 125 , if you want to have even more control over how much memory your browser uses, we’re introducing the new resource controls setting to set how much RAM Edge can use.

How to access resource controls

To enable the new resource controls setting, make sure you have Microsoft Edge version 125 or later and go to Settings and more (…) > Settings > System and performance. Under the Manage your performance section, switch the toggle to enable resource controls:

When you enable the setting, by default RAM usage is controlled only when you’re PC gaming. If you want to limit Edge’s RAM usage all the time, then select Always.

Note that, depending on the limit you set, resource controls can affect your browser performance. When you set a limit for the memory Edge can use, your browser functions normally until that limit is hit. When Edge hits the limit, the browser will try to reduce its memory usage and you may notice increased page reloads with more tabs being slept and discarded. Setting a low limit may slow down your browser performance.

How to keep an eye on browser performance

To keep a close eye on your browser performance, use the Browser essentials sidebar in Microsoft Edge. The sidebar now also lets you monitor your newly set RAM limit.

To open the Browser essentials sidebar, go to Settings and more (…) > Browser essentials:

Browser essentials let you toggle efficiency mode and monitor the memory usage related to sleeping tabs. And now, if you have enabled the new resource controls setting, the RAM usage section will also appear.

Note that there may be moments when the memory usage appears to be higher than your set limit. This is expected, Edge tries its best to keep usage below your set value but may not always be able to do so.

Try the new resource controls setting and Browser essentials, and let us know what you think! If you have any feedback or suggestions for this feature, let us know by sending feedback in Edge: go to Settings and more (…) > Help and feedback > Send feedback.

Source: Windows Blog
—

Today, we’re announcing the deprecation of the CSS -ms-high-contrast media query and -ms-high-contrast-adjust property, in favor of the standard-based forced colors feature that we implemented in Chromium-based browsers in 2020.

Contrast themes is a very important accessibility feature of Windows, which makes text more visible and easier to read. In the past, Internet Explorer and Microsoft Edge with the EdgeHTML engine, made it possible for websites to honor a user’s contrast theme setting by using the -ms-high-contrast and -ms-high-contrast-adjust CSS features. In 2020, we went one step further and worked with Chromium to standardize support for contrast themes on the web, so that it doesn’t only work in Edge, but also in any engine that implements support for the feature. We renamed the feature to forced colors. Today, forced colors support is supported in Chromium-based browsers as well as Firefox.

To learn more about the forced colors feature, check out the following links:

• The forced-colors media query can be used to detect when the browser is in forced colors mode. This mode matches the Windows contrast theme feature, but there could potentially be other similar forced colors modes in other operating systems in the future.
• The forced-color-adjust property controls whether the user agent’s system colors override should be applied to an element and its descendants while in forced colors mode.
• System color keywords can be used to apply colors in the user’s color scheme.
• Our 2020 announcement: Styling for Windows high contrast with new standards for forced colors.

Deprecating the legacy ms-prefixed CSS features

When we shipped the forced colors feature in Chromium-based Edge for the first time, we also wanted the websites that used the legacy CSS features from Internet Explorer and Microsoft Edge with the EdgeHTML engine to keep working. So, we maintained support for the -ms-high-contrast media query, and the -ms-high-contrast-adjust property.

Today, we’re announcing our deprecation process for these CSS features. Continue reading to learn what to expect, and how to migrate to the new properties.

Deprecation period

To reduce interoperability issues and to gather feedback, we plan to slowly deprecate the legacy -ms-high-contrast media query and -ms-high-contrast-adjust property in Microsoft Edge.

We are planning to completely disable the legacy implementation by Edge 138, but this plan might change depending on the feedback that we receive during this deprecation trial.

Testing the deprecation early

We’re introducing a way for you to check that your new forced color styles work correctly before we completely disable the legacy high-contrast implementation. To check your styles, you can disable the legacy implementation locally in Microsoft Edge:

• Open a new window or tab.
• Go to edge://flags/#edge-deprecate-ms-high-contrast in that tab.
• Enable the Deprecate ‘-ms-high-contrast’ and ‘-ms-high-contrast-adjust’ flag, and then restart Microsoft Edge.

DevTools warning

As part of the deprecation process, Microsoft Edge will also display a warning in the DevTools Console tool for any sites that use the legacy properties in their stylesheets starting with Edge version 126.

Origin trials

Finally, to make it possible for you to phase out the legacy implementation and keep your website functioning well after it’s been deprecated, we’re beginning an Origin Trial in Edge 132. See Microsoft Edge Origin Trials for more details.

In the time leading up to the deprecation, Microsoft Edge will be reaching out to accessibility testers and sites with known usage of the legacy properties to prevent breakages when the deprecation happens.

How to update your styles to the new forced colors standard

If your site uses the legacy -ms-high-contrast media query and -ms-high-contrast-adjust property to modify its styles when Windows is set to a contrast theme, we recommend that you adopt the new forced colors mode standard before the legacy properties are deprecated.

The table below shows how the legacy properties can be transferred to the new standards:

With Internet Explorer and Microsoft Edge with the EdgeHTML engine	With Microsoft Edge and other browsers that support forced colors
@media (-ms-high-contrast: active) {}	@media (forced-colors: active) {}
@media (-ms-high-contrast: black-on-white) {}	@media (forced-colors: active) and (prefers-color-scheme: light) {} Note: this is not exactly equal to the legacy black-on-white media query, which matched only specific default contrast themes. The new implementation will observe the luminosity of the user’s background color to determine whether prefers-color-scheme: light/dark is appropriate to match. In Chromium, a forced background with a luminosity of <0.33 will be a match for dark color schemes; otherwise, prefers-color-color-scheme: light will match.
@media (-ms-high-contrast: white-on-black) {}	@media (forced-colors: active) and (prefers-color-scheme: dark) {} Same note as the previous row.
-ms-high-contrast-adjust: none;	forced-color-adjust: none;

Note that there are some key differences that you’ll need to account for, when migrating your contrast theme styles to the new forced colors mode standard. These include changes to the style cascade, system color keywords, and native form controls design. For more details, please see Styling for Windows high contrast with new standards for forced colors.

How to test forced colors mode on your website

To check how your website renders when using a contrast theme, you can either change your Windows settings to use a contrast theme or emulate it via DevTools.

To change your Windows settings:

• On Windows 10: go to Settings > Ease of Access > High contrast, and then click Turn on high contrast.
• On Windows 11: go to Settings > Accessibility > Contrast themes, select a theme from the Contrast themes drop-down menu, and then click Apply.

If you want to test your website on other operating systems, such as macOS or Linux, or if you don’t want to change your Windows theme, you can also emulate the forced colors mode by using Microsoft Edge DevTools:

• Open DevTools by pressing F12 or Ctrl+Shift+I.
• Open the Rendering tool by clicking More tools (+) > Rendering.
• Scroll down to Emulate CSS media feature forced-colors.
• Select forced-colors:active to emulate forced colors mode. Or select forced-colors:none to stop emulating forced colors.
• You can also choose a specific forced colors theme by using the Emulate CSS media feature prefers-color-scheme dropdown menu and setting its value to either prefers-color-scheme:light or prefers-color-scheme:dark.

By using the emulation feature in DevTools, you can preview how your website will look to users of different contrast themes and adjust your styles accordingly.

Backwards compatibility

If you’re required to support contrast themes for both Internet Explorer and Microsoft Edge with the EdgeHTML engine, as well as newer versions of Microsoft Edge based on Chromium, we recommend using a combination of the legacy and standard properties for maximum compatibility.

For example, if your styles look like this:

Update these styles to with the following rules:

Let us know how things go

If you encounter any issues during your testing, please send us feedback in either of these two ways:

• To send us feedback directly from Microsoft Edge: go to Settings and more (…) > Help and feedback > Send feedback.
• Or, to report a problem directly with the Chromium implementation of the new forced colors mode standard, create a new issue using Chromium’s bug tracker.

Source: Windows Blog
—

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 22635.3566 (KB5037002) to the Beta Channel.

REMINDER: All Windows Insiders in the Beta Channel will now be on the same build (Build 22635.xxxx) via an enablement package. For Windows Insiders in the Beta Channel who want to be the first to get features gradually rolled out to you, you can turn ON the toggle (shown in the image below) to get the latest updates as they are available via Settings > Windows Update. Over time, we will increase the rollouts of features to everyone with the toggle turned on. Should you keep this toggle off, new features will gradually be rolled out to your device over time once they are ready.

Going forward, we will document changes in Beta Channel builds in two buckets: new features, improvements, and fixes that are being gradually rolled out for Insiders who have turned on the toggle to get the latest updates as they are available and then new features, improvements, and fixes available to everyone in the Beta Channel.

Changes and Improvements gradually being rolled out to the Beta Channel with toggle on*

[Taskbar & System Tray]

• In response to feedback, we are now showing the “show desktop” button by default and users can still manage this by right-clicking on the taskbar and choosing “Taskbar settings” (which opens Settings > Personalization > Taskbar directly).

[File Explorer] 

• Dragging-and-dropping files with your mouse between breadcrumbs in the File Explorer Address Bar that began rolling out with Build 22635.3420 is now available to all Insiders in the Beta Channel.

Fixes and Improvements for everyone in the Beta Channel

• New! This update improves the Widgets icons on the taskbar. They are no longer pixelated or fuzzy. This update also starts the rollout of a larger set of animated icons.
• New! This update affects Widgets on the lock screen. They are more reliable and have improved quality. This update also supports more visuals and a more customized experience for you.
• This update fixes an issue which was causing Settings to crash when copying out text in the last few flights.
• This update addresses an issue that affects universal printers. The system creates duplicate print queues for them.
• This update adds support for Arm64 .msi files using a Group Policy Object (GPO). You can now use the Group Policy Management Console (GPMC) to add Arm64 .msi files. You can also use a GPO to install these files on Arm64 machines.
• This update affects hypervisor-protected code integrity (HVCI). It accepts drivers that are now compatible.
• This update addresses an issue that occurs when you elevate from a normal user to an Administrator to run an application. When you use a PIN to sign in, the app will not run.
• This update affects Windows Subsystem for Linux 2 (WSL2). Intermittent name resolution fails in a split DNS setup.
• This update addresses an issue that affects the netstat -c It fails to perform effective port exhaustion troubleshooting.
• This update addresses an issue that affects a low latency network. The speed of data on the network degrades significantly. This occurs when you turn on timestamps for a Transmission Control Protocol (TCP) connection.
• This update addresses an issue that affects the Distributed Transaction Coordinator (DTC). A memory leak occurs when it retrieves mappings.
• This update includes quarterly changes to the Windows Kernel Vulnerable Driver Blocklist file, p7b. It adds to the list of drivers that are at risk for Bring Your Own Vulnerable Driver (BYOVD) attacks.
• This update affects the touch keyboard. It makes the Japanese 106 keyboard layout appear as expected when you sign in.
• This update adds a new mobile device management (MDM) policy called “AllowScreenRecorder.” It affects the Snipping Tool. IT admins can use this policy to turn off screen recording in the app.
• This update addresses an issue that affects Bluetooth Advanced Audio Distribution Profile (A2DP) hardware offload. A stop error occurs on PCs that support it.
• This update addresses a memory allocation issue in the Host Networking Service (HNS). The issue causes high memory consumption. It also affects service and pod deployment and scaling.
• This update addresses an issue that affects the container networking Address Resolution Protocol (ARP). It returns the wrong Virtual Subnet ID (VSID) for external ports.
• This update affects media allocations. It improves their memory granularity for some hardware setups. This lowers overcommitment. Also, performance is more efficient.
• This update addresses an issue that affects an accelerator backing store management path. A memory leak occurs that affects some devices.
• This update addresses an issue that affects Windows Local Administrator Password Solution (LAPS). Its Post Authentication Actions (PAA) do not occur at the end of the grace period. Instead, they occur at restart.
• This update addresses a race condition that might stop a machine from starting up. This occurs when you set up a bootloader to start up multiple OSes.
• This update makes Country and Operator Settings Asset (COSA) profiles up to date for some mobile operators.
• This update addresses an issue that affects the Resilient File System (ReFS). A high load might make the system unresponsive. Also, signing in might be slow.
• This update addresses an issue that affects Settings. It stops responding when you dismiss a flyout menu.
• This update addresses an issue that affects Protected Process Light (PPL) protections. You can bypass them.

Known issues

[General]

• We are investigating an issue where Internet Information Services (IIS) and Windows Communication Foundation (WCF) may not work after installing this update.

[Copilot in Windows*]

Windows Insiders in the Beta Channel who have the updated Copilot in Windows experience that introduces the ability for Copilot to act like a normal application window may see the following known issues:

• We are aware of reports by Insiders in the Canary and Dev Channels that Copilot is auto-launching unexpectedly after restarting their PCs. We hope to have a fix for this issue soon and is unrelated to the auto-launching experience we tried out with Insiders in the Canary and Dev Channels in early Februarywhich we stopped rolling out in March.
• Voice access does not work reliably with the updated Copilot in Windows experience that introduces the ability for Copilot to act like a normal application.
• Using Windows Ink to write in Copilot will not work with the updated Copilot in Windows experience.

[Widgets]

Windows Insiders in the Beta Channel who have the new position for the Widgets entry-point on left-aligned taskbars may see the following known issues:

• Swipe invocation for Widgets may not work if taskbar is center-aligned instead of left-aligned.
• Unpinning Widgets from the taskbar may not work if taskbar is center-aligned instead of left-aligned.
• The Widgets board is incorrectly positioned when Copilot is in side-by-side mode.
• Turning on/off Widgets in taskbar settings may refresh the taskbar.

About the Beta Channel

The Beta Channel is the place we preview experiences that are closer to what we will ship to our general customers. 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. However, this does not mean every feature we try out in the Beta Channel will ship. We encourage Insiders to read this blog post that outlines the ways we’ll try things out with Insiders in both the Dev and Beta Channels.

*Getting new features: For Windows Insiders in the Beta Channel who want to be the first to get features gradually rolled out to you, you can turn ON the toggle to get the latest updates as they are available via Settings > Windows Update. Over time, we will increase the rollouts of features to everyone with the toggle turned on. Should you keep this toggle off, new features will gradually be rolled out to your device over time once they are ready.

**Availability of Copilot in Windows: Copilot in Windows in preview is being rolled out gradually to Windows Insiders in select global markets. The initial markets for the Copilot in Windows preview include North America, United Kingdom and parts of Asia and South America. It is our intention to add additional markets over time.

Important Insider Links

• Want to learn how we made Windows 11? Check out the 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.

Thanks,
Amanda & Brandon

Source: Windows Blog
—

Manor Lords is out today on the Microsoft Store and via PC Game Pass (Game Preview).

A city-building and strategy game that focuses on sandbox gameplay and intimate historical details, the game delivers authentic building designs, workplaces and fashion. But if you’re not careful there can be a downside to the authenticity – your people will starve if you don’t adequately prepare for the colder months.

Head over to Xbox Wire for some tips and tricks on establishing yourself as a new Lord and keeping your settlers happy.

Source: Windows Blog
—