HomeGame Guides"Show Desktop" button works by default with Windows 11 beta channel build...

“Show Desktop” button works by default with Windows 11 beta channel build 22635.3566

Published on

When you purchase through links on our site, we may earn an affiliate commission. That’s how it works.

John Kelham

Newwin
·

Apr 26, 2024 1:18 PM EDT

Microsoft has released a new build of Windows 11 for members of the Windows Insider program in the beta channel. The new build number is 22635.3566 (KB5037002). This re-enables the “Show Desktop” button on the taskbar by default, among other improvements and bug fixes.

Here is the changelog:

Changes and improvements are gradually rolled out to the beta channel upon activation

[Taskbar & System Tray]

  • In response to feedback, we’re now showing the “Show Desktop” button by default and users can still manage this by right-clicking on the taskbar and selecting “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 started 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 widget icons on the taskbar. They are no longer pixelated or blurry. This update also begins the rollout of a larger set of animated icons.
  • New! This update affects lock screen widgets. They are more reliable and their quality is improved. This update also supports more visuals and a more personalized experience for you.
  • This update fixes an issue that caused settings to crash when copying text on recent 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 compatible drivers now.
  • This update addresses an issue that occurs when you switch from a standard user to an administrator to run an application. When you use a PIN to sign in, the app won’t work.
  • This update affects the Windows Subsystem for Linux 2 (WSL2). Intermittent name resolution fails in a split DNS setup.
  • This update addresses an issue affecting netstat -c that fails to perform effective port extraction troubleshooting.
  • This update addresses an issue affecting a low-latency network. The data speed in the network decreases significantly. This occurs when you enable timestamps for a Transmission Control Protocol (TCP) connection.
  • This update addresses an issue affecting 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. This adds to the list of drivers that are at risk of Bring Your Own Vulnerable Driver (BYOVD) attacks.
  • This update affects the touch keyboard. This causes the Japanese 106 keyboard layout to appear as expected when entering.
  • This update adds a new Mobile Device Management (MDM) policy called “AllowScreenRecorder”. This affects the cutting tool. IT administrators can use this policy to turn off screen recording in the app.
  • This update addresses an issue affecting the Bluetooth Advanced Audio Distribution Profile (A2DP) hardware offload. A stop error occurs on computers that support it.
  • This update addresses a memory allocation issue in the Host Network Service (HNS). The problem causes high memory consumption. This also affects service and pod deployment and scaling.
  • This update addresses an issue that affects the Container Networking Address Resolution Protocol (ARP). This returns the wrong virtual network identifier (VSID) for external ports.
  • This update affects media allocations. This improves their memory detail for certain hardware settings. It reduces overcommitment. Also, the performance is more efficient.
  • This update addresses an issue affecting the accelerator backup store management path. A memory leak is occurring that affects certain devices.
  • This update addresses an issue affecting the Windows Local Administrator Password Solution (LAPS). Its post-authentication (PAA) actions do not occur at the end of the grace period. Instead, they occur on restart.
  • This update addresses a race condition that could stop the computer from starting. This occurs when you configure boot to run multiple operating systems.
  • This update makes the Country Assets and Operator Settings (COSA) profiles up to date for some mobile operators.
  • This update addresses an issue affecting the Resilient File System (ReFS). A high load may cause the system to become unresponsive. Also, login may be slow.
  • This update addresses an issue affecting settings. It stops responding when you disable exit menu.
  • This update addresses an issue affecting Protected Process Light (PPL) protections. You can bypass them.

known problems

[General]

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

[Copilot in Windows]

  • Windows Insiders in the beta channel who have the updated Copilot experience on Windows that introduces the ability for Copilot to act like a normal application window may see the following known issues:
  • We are aware of reports from Insiders in the Canary and Dev channels that Copilot is automatically running unexpectedly after restarting their PCs. We hope to have a fix for this issue soon, and is not related to the auto-launch experience we tried with Insiders on the Canary and Dev channels in early February, which we stopped rolling out in March.
  • Voice access doesn’t work reliably with the updated Copilot experience on Windows that introduces Copilot’s ability to act like a regular app.
  • Using Windows Ink to write in Copilot will not work with the updated Copilot experience on Windows.

[Widgets]

  • Windows Insiders in the beta channel who have the new location for the Widgets entry point on left-aligned taskbars may see the following known issues:
  • Enabling swipe for widgets may not work if the taskbar is center-aligned instead of left-aligned.
  • Unpinning widgets from the taskbar may not work if the taskbar is center-aligned instead of left-aligned.
  • The Widgets panel is positioned incorrectly when Copilot is in side-by-side mode.
  • Enabling/disabling widgets in the taskbar settings may refresh the taskbar.

You can check the Full blog post here.

Report a problem with the article

previous article

Microsoft is adding Planner Premium Plan tasks to the new Planner app under the My Tasks view

Latest articles

More like this