Microsoft today released Windows 10 Redstone Build 14295 to Windows Insiders in the Fast ring for PC and Mobile. This comes on the heels of the last week’s Redstone Build 14291 which included extension support for Microsoft Edge as well as other new features.
This build isn’t as exciting as the last, but it does include a lot of fixes and performance improvements.
If you’re testing Redstone on your Windows Phone, it’s worth noting that in addition to the retail models i.e. Lumia 550 or Lumia 950, there are some older models that will be capable of running it. Microsoft has a list of phones that support the Mobile Insider Preview. The company does state that the only exception is the Lumia 635. Microsoft says it will be added at a later date.
Windows 10 Redstone Build 14295
According to Microsoft exec Gabe Aul, the following issues have been fixed for PC:
- We fixed the issue that was causing PCs to freeze when plugging in an Xbox One or Xbox 360 controller and other gamepads.
- We fixed an issue where Microsoft Edge would refresh the tab if you pressed caps lock in a password field.
- We fixed an issue preventing the Xbox app and other Xbox Live enabled apps and games from signing in.
- We have fixed the driver bug that prevents Kaspersky Anti-Virus, Internet Security, or the Kaspersky Total Security Suite installed from working as expected in builds from the Development Branch.
The following fixes are for the Mobile version
- We fixed the issue where if you reset your phone on Build 14291 and restore your phone from a backup, restore will fail to install apps from your backup’s apps list leaving blank grey titles on Start. You should be able to reset your phone on this build, do a restore from a backup, and have your apps installed and restored appropriately.
- We fixed an issue where new languages and keyboards were not downloading. However, there is an issue where the “reboot” UX doesn’t appear in the Settings app after downloading a new language or keyboard. You will need to go to Update & security > Phone update and restart your phone manually from there for the new language and keyboard to go into effect.
There is a long list of known bugs, however.
Known Windows 10 Build 14295 PC Issues
- We are aware of issues with Narrator and other screen reader apps being unable to read the menu options in the Feedback Hub, as well as issues with Narrator not reading selected text in the Feedback Hub, Cortana, and other apps. We’re working diligently to fix these bugs as soon as possible and apologize to Insiders impacted by this.
- If you use Hyper-V and have a Virtual Switch configured for your network adapter, you may see an error indicator (red-colored “X”) for your network adapter in the notification area of your taskbar. The error indicator is incorrect and your network adapter should continue to work just fine.
- On some PCs with TPM chips, such as the ASUS Zenbook UX31, you may experience glitchy audio and jumpy movement when using the trackpad due to the “tpm-maintenance” task running constantly in the background instead of once per boot-up like it should. As a temporary workaround, you can disable the tpm-maintenance task in Task Scheduler (under \microsoft\windows\tpm).
- PCs that use Windows Hello or a PIN to sign-in to the device will launch the Microsoft Passport service. When this happens, there is an issue in this build where Bluetooth will then repeatedly scan for devices. This causes a few issues on the PC including reduced battery life, audio glitches, responsiveness issues with Bluetooth keyboards and mice, a decrease in Wi-Fi throughput on Wi-Fi/Bluetooth combo chipsets, and a decrease in throughput for Bluetooth file transfers. As a workaround, you can disable the Microsoft Passport (NgcSvc) service by opening an elevated Command Prompt, run “reg add HKLM\System\CurrentControlSet\Services\NgcSvc /v Start /t REG_DWORD /d 0x4 /f” and then reboot. However, you will not be able to use Windows Hello or a PIN to sign-in to your device. The service will be re-enabled again when you update to the next build.
- After upgrading to this build from Build 14291, attempting to connect to a Miracast receiver the connection will fail. The workaround to get out of this state is to go to this registry key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\
Parameters” and select “StandaloneDhcpAddress” and change the value from “192.168.173.1” to “192.168.137.1” (value type is REG_SZ). Then retry the connection to the Miracast receiver.
- We are seeing reports of some apps such as QQ crashing. We are currently investigating, and this bug may also impact older apps such as Windows Live Mail and Expression Encoder 4.
Of course, there is known issues with the Mobile build as well.
Known Windows 10 Mobile Build 14295 Known Issues
- After updating to the most recent builds from our Development Branch, a system API failure occurs after the update that causes the Microsoft Band 1 or 2 to have sync issues. To get out of this bad state, you can reset your phone on this build, re-pair your Microsoft Band, and syncing should work again.
- After upgrading to this build from a previous build from our Development Branch, attempting to connect to a Miracast receiver the connection will fail. There is no workaround for this issue unfortunately on Mobile.
- The Gadgets app will not detect the Microsoft Display Dock on phones running Windows 10 Mobile Insider Preview builds, and thus cannot update the firmware version. If you have a dock which has already been updated to version 4 then this will not affect you. If you have a dock that has not been updated, then you may experience some minor issues with USB-C stability. You will still be able to use your dock and Continuum.
As with all Insider builds, this one will take a while as it’s an in-place upgrade. A restart is required and the amount of time it takes to install will vary for each person.
After the installation of this new build completes, you can hit Windows Key + R to bring up the Run dialog and type: winver and hit Enter. That will show you the new version as Build 14295.
Once you have the latest build installed, let us know what you think of it and any problems you’re experiencing in the comments below. Or, for a more in-depth conversation, check out our new and improved Windows 10 Forums!
Wouldnt it be nice if we got a build that just fixed things without an even longer list of whats broken.