True to its promise to release builds at a faster rate, Microsoft has released another new build of Windows 10 to Fast ring users but there are no new features in this release. But, there are quite a few bugs fixed with this build but also new issues introduced.
In this release, posted below, are quite a few bugs that have been squashed but just because these items have been patched, you should still avoid running this build on your primary machine.
Bugs fixed in this build:
- The issue of periodic app crashes or other memory related app errors due to a memory management change has been resolved. If you were having issues launching the Git client for Windows, you should now be able to launch it in this build.
- The Connect button now shows up again in Action Center.
- F12 Developer Tools will now load correctly Microsoft Edge.
- We fixed an issue where suggested apps were being shown on the Start menu even though “Occasionally show suggestions in Start” was turned off under Settings > Personalization > Start.
- We fixed an issue where if you try to change the Lock screen picture with “Get fun facts, tips, tricks and more on your lock screen” turned on it will revert back to the default.
- We fixed an issue where the positions of desktop icons get jumbled up after switching DPI settings from 100% to 150% or 175%.
- We also fixed an issue where pasting files into a new .zip file (compressed folder) in File Explorer by either right-clicking or Control-V would not work. You should be able to paste tiles into new .zip files just fine now.
If you are in the Fast ring, you can download this build right now but you should be aware of the issues in this release which are posted below.
- If you choose “Reset This PC” under Settings > Update & Security > Recovery – your PC will be in an unusable state. There is no workaround if your PC gets into this state and you will need to reinstall Windows. This issue will be fixed in the next build. You can still rollback to the previous build if for some reason this build doesn’t work out for you. This bug also existed in Build 14251 so please avoid resetting your PC on these builds.
- You might see a WSClient.dll error dialog after logging in. We’re working on a fix for this but as a workaround, you can run the following in Command Prompt with administrative rights: schtasks /delete /TN “\Microsoft\Windows\WS\WSRefreshBannedAppsListTask” /F. This issue will be fixed in the next build.
- The front-facing camera is unusable on PCs with Intel RealSense resulting in being unable to use Windows Hello or any other apps that utilize the front-facing camera.
- After logging in to your PC, you may hit a UI issue in which Airplane Mode will incorrectly show as “on” even though your PC’s Wi-Fi is powered on. This is due to a timing issue between how the UI communicates and waits for the underlying platform to respond. The UI for Airplane Mode essentially does not wait long enough for the device’s physical radios to power on before reporting the current state. You can toggle the Airplane Mode on and off to get Airplane Mode back to showing the correct state.
Let us know if you run into any new issues with this release or if you happen to find any secrets that could unveil upcoming features to the platform. You can read the announcement post for this release, here.
Tagged with Windows 10