KB5044377: Discover Dynamic Lighting Changes in Windows 11 Insider Beta Build 22635.4435

Microsoft has unveiled a new Windows 11 build for participants in the Windows Insider Program within the Beta channel, designated as build 22635.4435 (KB5044377). This version introduces a keyboard shortcut for administrators, enhancements to dynamic lighting capabilities, and resolves several bugs. Additionally, it reinstates the option to configure the Copilot key, which was removed in earlier Beta releases.

Here’s an overview of the changes:

Improvements and Changes Gradually Rolled Out in the Beta Channel

[General]

Now, if you hold Shift and CTRL while selecting an item from the jump list in the Start menu or taskbar, it will open that item with administrator privileges, similar to directly clicking the app icon with the same key combination. For instance, if you right-click on Windows Terminal and then click on PowerShell while holding Shift and CTRL, it will launch PowerShell with admin access.

[Dynamic Lighting]

• When no compatible devices are connected, the Dynamic Lighting settings page will display a placeholder message, and the Brightness and Effects controls will be disabled.
• New directional options—Forward, Backward, Outward, and Inward—have been added to the Wave effect on the Dynamic Lighting settings page, along with a Forward option for the Gradient effect.

Fixes being gradually rolled out to the Beta Channel

[Taskbar]

• Resolved an issue where the WIN + keyboard shortcut was not functioning in certain scenarios in recent flights.
• Fixed a problem where the close (X) button on the taskbar wasn’t responding for some Insiders.

[Input]

• Addressed an issue where the mouse would unlock from a game window on systems with multiple monitors after the Game Bar was opened and closed, preventing use within the game.

Further Updates and Fixes for Everyone in the Beta Channel

[Settings]

• After the Copilot key configuration option was disabled in Build 22635.4291, it has now been reinstated with updates. The apps that can be launched using the Copilot key have been restricted to those that choose to participate in this feature. This adjustment ensures that targeted apps are aware of their usage in this manner and comply with security and privacy standards for user safety. Detailed guidance for app developers on opting into this feature will be published soon on the Microsoft Learn page. You can access this setting via Settings > Personalization > Text input.

General Fixes for All Beta Channel Users

[Other]

This update addresses a variety of issues, including:

• [Bluetooth] Fixed: Resolved a memory leak issue that caused an app to become unresponsive.
• [Product Activation Phone Numbers] Fixed: New phone numbers are added for various regions.
• [Collector Sets] Fixed: Ensured proper closure of collector sets when an exception occurs during startup or while active. Previously, the command to stop a collector set would become unresponsive.
• [Windows Kernel Vulnerable Driver Blocklist file (DriverSiPolicy.p7b)] This update expands the list of drivers identified as being susceptible to Bring Your Own Vulnerable Driver (BYOVD) attacks.
• [Windows Hello for Business] Fixed: Corrected an issue where PIN reset failed when selecting the “I forgot my PIN” link on the credential screen.
• [Multi-Function Printer (MFP)] Fixed: Resolved an issue that caused specific network command text to print when connected via USB, contrary to user intent.
• [Microsoft Teams] Fixed: Fixed a problem preventing users from joining Teams meetings when responding to an Outlook meeting reminder.
• [Country and Operator Settings Asset (COSA)] Fixed: Updated profiles for specific mobile operators.
• [vmswitch] Fixed: Resolved a stop error triggered by a vmswitch when employing Load Balancing and Failover (LBFO) teaming across two virtual switches on a virtual machine, where one switch utilizes single root Input/Output virtualization (SR-IOV).
• [WebView2 apps] Fixed: Addressed input detection issues from Xbox 360 and Bluetooth controllers in WebView2 applications.

For more detailed information, you can view the complete blog post here.

Source