Microsoft is rolling out its latest Week D Windows 11 preview updates, delivering a fresh batch of features and system improvements ahead of June’s mandatory Patch Tuesday. Designed for early adopters and power users, these optional updates introduce highly requested capabilities like shared audio over Bluetooth LE and the ability to set a custom user folder name during the initial operating system setup.
For users currently running Windows 11 versions 24H2 and 25H2, Microsoft is offering the optional KB5089573 update. Installing this patch bumps the operating system to builds 26100.8524 and 26200.8524, respectively. This release allows users to test core stability improvements before they are pushed to the general public next month.
Meanwhile, users testing the cutting-edge Windows 11 version 26H1 are no longer lagging a month behind the standard release cycle. They can now install KB5089570, which upgrades the system to build 28000.2179 and brings their feature set into alignment with the older branches.
New Features and System Improvements
The key new features and changes in these preview updates are identical across all supported versions of Windows 11. If you choose to install the optional patch, you will receive the following upgrades:
- Shared audio support over Bluetooth LE.
- Multi-app camera support.
- Choose a custom name for your user folder during Windows Setup.
- Improvements to Magnifier, Secure Boot (in Windows Security), Task Manager, Windows Hello, and Windows Search.
- Performance improvements for app and core system experiences.
- Reliability improvements for the sign-in and Lock screens.
The End of the Truncated Folder Name
While the addition of Bluetooth LE audio sharing is a great modern connectivity upgrade, the most impactful change for PC builders and IT admins is the ability to choose a custom user folder name during setup. For years, Windows 11 has automatically truncated Microsoft Account names to create the local user profile folder, often resulting in ugly, five-letter gibberish directories that users could not easily change without risking registry corruption.
Furthermore, bringing version 26H1 back into alignment with the 24H2 and 25H2 update schedules indicates that Microsoft is tightening its development pipeline. By synchronizing these builds, the Windows engineering team can gather more consistent telemetry across all active branches before finalizing the mandatory security patches for June.
