The insiders on the Dev Channel received Windows 11 preview Build 25169 today. The new build brings the long-awaited Windows Spotlight and the brand-new multi-app Kiosk Mode. For the rest, some fixes and improvements.
Changed in Windows 11 Build 25169
[Multi-App Kiosk Mode]
Multi-app kiosk mode is a lockdown feature for Windows 11 that allows an IT administrator to select a set of allowable apps to run on the device, while all other functionalities are blocked. This enables you to create multiple different apps and access configurations for different user types, all on a single device.
Some lockdown customizations include:
- Limiting access to Settings, except selected pages (e.g., Wi-Fi and screen brightness)
- Lock down the Start menu to show only allowed apps.
- Block toasts and pop-ups that lead to unwanted UI.
Multi-app kiosk mode is ideal for scenarios in which multiple people need to use the same device. This can include frontline workers and retail scenarios, education and test taking.
Currently, multi-app kiosk mode can be enabled using PowerShell and WMI Bridge, with support for Intune/MDM and provisioning package configuration coming soon.
To configure using WMI, follow these instructions. Using the Windows 10 sample XML will enable the feature, but will result in an empty Start menu. To populate the Start menu with your apps, follow these instructions to generate the list of pinned apps, then add it to your XML file after closing the StartLayout section, like the below:
DATA[ <em>Your JSON here </em>]]></win11:StartPins>
- The changes noted here in this previous blog post on changes to how IT admins enroll devices in the Windows diagnostic data processor configuration option are now included in this build (Build 25169 and higher). A reminder that if the documented changes are not acceptable, it is recommended to pause flighting.
- You can now enable Windows Spotlight on the desktop via a brand-new Windows Spotlight theme now included in the latest builds in the Dev Channel under Settings > Personalization and Settings > Personalization > Themes. Additionally, you can make your own custom themes with Windows Spotlight’s rotating images as well.
- We have updated the U.S. English (EN-US) handwriting model to be faster and more accurate. Use the updated Handwriting Panel for ink-to-text and let us know what you think.
- Settings now supports managing apps which were earlier only supported from Control Panel. This includes uninstallation of apps which have inter-dependencies (e.g., Steam and gaming apps running on Steam), repair and modifying of Win32 apps.
- The Windows Security app version is now displayed in Windows Security settings under About.
- Fixed an issue leading to the Azure Information Protection context menu entry unexpectedly showing with the name Microsoft.Azip.RightClick after an upgrade.
- Fixed an explorer.exe crash that was preventing taskbar from loading when launching Microsoft Teams meetings sometimes.
- Fixed a couple explorer.exe crashes some Insiders were experiencing related to taskbar overflow.
- Fixed an issue that was removing the “More” button in Start’s Recommended section.
- Fixed an issue where after using the reveal password button in the Wi-Fi section of Quick Settings, the text field might unexpectedly lose focus.
- We made a small tweak to improve the key repeat rate for the traditional touch keyboard layout, as well as the default touch keyboard layout, so it feels more responsive. Now it has the rate of 20 keys per second (for example, when holding down the delete key).
- Fixed an issue believed to be the root cause of some Insiders experiencing bug checks when opening and copying files from network locations recently.
- Fixed an issue which could cause desynced audio when recording game play with the Xbox Game Bar.
- Fixed an issue leading to error code 0x80004005 when using the network troubleshooter.
- Made some adjustments to fix an issue where the scrollbar in certain places (like File Explorer) was unexpectedly wide when using high DPI scaling.
- Fixed an issue believed to be the root cause of Windows Security saying standard hardware security wasn’t supported on devices where it was actually supported, as well as showing a warning in the taskbar but not showing any issues when Windows Security was launched. Please note, due to timing of the payload, these issues may come back after the next Windows Security update. It will go away again after a future Windows Security update.