This week, Microsoft has unveiled a new preview build of Windows 11, designated as 22635.4870 or KB5050087, within the Beta Channel. Among the most significant enhancements introduced is the newfound ability to customize lock screen widgets, allowing users to select which widgets are displayed when their PC is locked.
Enhanced Customization for Lock Screen Widgets
While lock screen widgets are not a novel concept—having been available since the introduction of Windows 10—they were first brought to the forefront in 2024. These widgets serve as a convenient means to access essential information at a glance. However, initial feedback from users, including reports from Neowin, highlighted a limitation in personalization options: users could only toggle all widgets on or off, with no middle ground. The first indications of the current customization feature emerged in November 2024.
The rollout of this customizable feature is currently underway for Windows Insiders using build 22635.4870 in the Beta Channel. For those eager to explore this functionality without waiting for the gradual rollout, here’s a step-by-step guide to enable it manually:
- Download ViVeTool from GitHub and extract the files into a folder that is easy to locate.
- Open Command Prompt as an Administrator and navigate to the folder containing the ViVeTool files using the CD command. For instance, if ViVeTool is located in C:Vive, you would type CD C:Vive.
- Enter vivetool /enable /id:50179255,53672489 and hit Enter.
- Restart your computer to apply the changes.
Once the system reboots, users can navigate to Settings > Personalization > Lock screen and select Your Widgets > Add Widget to customize their lock screen experience. For those who prefer not to utilize lock screen widgets at all, simply toggle off the Your Widgets option.
It is important to note that modifying these settings necessitates an activated Windows installation. Therefore, if you are experimenting with Windows 11 preview builds on a virtual machine, ensure that it is activated with a legitimate Windows key prior to making any changes. Some former Microsoft employees have shared intriguing insights regarding this requirement.
Credit for the feature IDs goes to @phantomofearth.
