Microsoft today is releasing Windows 10 build 21359 to Insiders in the Dev Channel. Here’s a look at what’s new.
Microsoft today is releasing Windows 10 Build 21359 to Insiders in the Dev Channel. This release is the follow-up to build 21354. There is one notable change to the Start menu for restarting apps and the rest is other improvements and fixes. Here is a look at what you can expect.
Windows 10 Build 21359
The most notable change in this build is a Start Menu option that lets you restart apps after signing in when you reboot your device. You can find it under Settings > Accounts > Sign-in options > Restart apps. When it’s enabled you will see the following option in the Start menu.
Here is the list of other changes and improvements:
- If you have your activity history synced across your devices through your Microsoft account (MSA), you’ll no longer have the option to upload new activity in Timeline. AAD-connected accounts won’t be impacted. To view web history, Edge and other browsers have the option to look back at recent web activities. You can also view recently used files using OneDrive and Office.
- We’re updating the Ease of Access category in Settings to now be called Accessibility.
- We’re updating the Ebrima font to now support characters from Bamum (Unicode block U+A6A0 to U+A6FF).
- We’re updating the Nirmala UI font family to improve how the Chakma characters are displayed when combined based on feedback.
- Thank you to the Insiders who have taken the time to share feedback about the new version of our Korean IME. For the time being we will be reverting to the version included in previous releases.
And here is the list of fixes contained in today’s new build:
- We fixed a bug that caused an issue when HDR was turned on, where the SDR content was being changed when the computer was locked or coming back from sleep.
- We fixed the issue where in in some cases, Auto HDR might not correctly enable for all eligible titles. If you still run into trouble, please reach out to us via the Feedback Hub, on our Twitter (@DirectX12), or on the DirectX Discord.
- We fixed the issue in the previous flight where in some cases user accounts were migrated during the upgrade, but the user profile was not. This issue would occur if a device was abruptly restarted during the upgrade process.
- We fixed an issue where some cameras did not support adjustment in the Camera Settings page when the camera was also in use by another app.
- We fixed an issue where the Camera Settings page was crashing on ARM devices.
- We fixed an issue where Windows Update Settings might unexpectedly display two separate strings saying that updates are managed by your organization.
- We fixed an issue where some non-managed devices were displaying “Some of these settings are hidden or managed by your organization” on the Settings > Update & Security > Windows Update page.
- We fixed an issue impacting WSUS users where the “Check online for updates from Microsoft Update” option in Windows Update Settings was greyed out.
- We fixed an issue resulting in some Insiders noticing frequent crashes in wuauclt.exe.
- We fixed an issue resulting in the window frames losing their shadows after locking and unlocking your PC.
- We fixed an issue resulting in some users seeing an ms-resource:AppListName entry in the Start menu apps list because of the People app change to no longer be displayed in the app list.
- We fixed an issue that could result in a toast notification appearing on top of the Action Center.
- We fixed an issue in recent flights where the UI would hang if you quickly used the touchpad gesture to switch back and forth between Virtual Desktops.
- We fixed an issue impacting the ability to use Miracast with some devices in recent builds.
- We fixed an issue that could result in the network connection on certain device and ethernet configurations getting stuck in an “Identifying…” state recently.
- We fixed an issue where after upgrading to recent builds you couldn’t connect using remote desktop until you rebooted your PC.
- We fixed an issue resulting in the brightness controls behaving erratically on some devices in recent builds.
- We fixed an issue impacting some Insiders when playing certain full screen games in recent builds, resulting in the frame rate being unexpectedly lowered. If you continue experiencing issues in this space, please log feedback following the steps here.
- We fixed an issue resulting in some games crashing on launch when Auto HDR was enabled.
- We fixed an issue for certain devices that could result in the screen going black with only the mouse visible. If you continue experiencing black screen issues after upgrading, please press WIN + CTRL + Shift + B and then report it in the Feedback Hub under Display and Graphics > Black Screen, including as many details as possible.
- We fixed an issue resulting in certain videos displaying distorted and pixelated in recent builds.
- We fixed an issue where some devices received “The follow things need your attention…” error messages when attempting to install a new build.
- We fixed an issue where getting and setting your international settings wasn’t working with PowerShell 7.1.
- We fixed an issue where updates to your language list using the PowerShell commands wouldn’t be synced to your other devices if you had syncing enabled.
- We fixed a race condition when using the Pinyin IME that could result in no longer being able to type in certain apps (until restarting the app) if you rapidly typed and selected IME candidates.
- We fixed the issue impacting the migration of shortcuts into the new Windows Tools location where This PC shows up with the display name “computer.”
It’s important to note that Insider builds are meant for coders, IT admins, and Windows 10 enthusiasts who want to test new features and submit feedback to Microsoft.
These builds are not meant for inexperienced users. They are also not meant to run on your primary production machine. Insider builds contain many known stability issues that can cause your system to become unstable or even crash.
For more on this build’s full list of changes, known issues, and workarounds make sure to read Microsoft’s full blog post.