Windows 11 Build 26120.1542 (Dev) places Widgets on the right side of the taskbar

Microsoft has release Windows 11 Build 26120.1542 to Insiders in the Dev channel. It introduces a new location for the widget button on the taskbar. For users who keep the start button on the left, Widgets will now have a bigger button on the right, next to the system tray.

Note that some of the changes in the Dev channel are first coming to Insiders who have enabled the "Get the latest updates as soon as they're available" option on the Settings > Windows Update page.

Changes for Insiders with the option enabled

New location of the Widgets button on the taskbar

If the taskbar is left-aligned, the taskbar's Widgets button will now appear on the left side of the system tray. The button itself has been made slightly wider to accommodate more useful content. The widgets panel will also now appear on the right side of the screen instead of the left.

Changes and improvements

Taskbar and system tray

The taskbar now supports navigation by the first letter of an application. You can set the focus to the taskbar with Win + T, and then press any letter to quickly jump to an open or pinned application whose name begins with that letter. Pressing the same letter again will switch between applications that begin with that letter, if there are several. If you have taskbar grouping disabled, navigation by the first letter will take into account the window name, not the application name. And when you press the Home and End  keys , the keyboard focus will move to the first and last elements of the taskbar, respectively.

Fixes

Input

• Fixed an issue where text hints for the hardware keyboard would not work correctly (the selected option would be merged with the original one).
• Fixed an issue where the emoji panel would close when trying to switch to the Symbols or Kaomoji sections after selecting an emoji.

Other

• Fixed an issue with Registry Editor where pasting a hexadecimal (HEX) value into a DWORD or QWORD field could cause the stored value to differ from the value entered (for example, 0x411 would be stored instead of 0x1).

For all insiders

General

Fixed an issue where adding additional languages ​​and features could fail with error code 0x800f081f.

Other

• • Windows kernel vulnerable driver blocklist file (DriverSiPolicy.p7b). New drivers at risk of Bring Your Own Vulnerable Driver (BYOVD) attacks have been added to the list.
  • Group Policy settings for Item Level Targeting (ILT) and Local Users and Groups. You cannot select a group from the target domain for ILT or an account from Local Users and Groups because the forest is not displayed. This issue occurs when multiple forests are deployed and the target domain has a one-way trust with the administrator domain, which affects Enhanced Security Admin Environment (ESAE), Hardened Forests (HF), or Privileged Access Management (PAM).
  • NetJoinLegacyAccountReuse:
    • Removed the NetJoinLegacyAccountReuse registry key to improve security when joining a domain. For more information, see KB5020276—Netjoin: Domain join hardening changes .
  • The Share button with Game Bar function did not work on USB controllers.
  • GPU-paravirtualized virtual machines and containers: After reboot, a graphics rendering issue could occur, affecting the stability of virtual machines and containers.
  • Domain Name System (DNS):
    • Enhanced DNS server security to address CVE-2024-37968 vulnerability. If domain settings are not updated, a SERVFAIL error or a timeout may occur.
  • PowerShell and VBScript: Fixed issues with using the Windows Update Agent API (WUA) API address in scripts.
  • BitLocker: The firmware update may fail if you have BitLocker encryption enabled.

Fixes

General

[Important note] Insiders who join the Dev channel on devices running Windows 11 Version 24H2 (Build 26100.xxxx) will see “(repair version)” next to the new build name in Windows Update. This is normal behavior and will update the system to the latest build for the Dev channel.

Task Manager

Switching between pages in Task Manager may cause it to crash.

Source