Microsoft rolls out Windows 10 build 16176 and 15204 for PC and Mobile Insiders
Microsoft is today rolling out two new Windows 10 Insider Preview builds for PC and Mobile for Insiders in the Fast ring today. The builds in question are 16176 for PC, and peculiarly 15204 for Mobile. Microsoft says Windows 10 Mobile builds will be issues from a different branch than that of the PC Insider Program from here on out.
Also, these new builds are available for the following handsets only:
- HP Elite x3
- Microsoft Lumia 550
- Microsoft Lumia 640/640XL
- Microsoft Lumia 650
- Microsoft Lumia 950/950 XL
- Alcatel IDOL 4S
- Alcatel OneTouch Fierce XL
- SoftBank 503LV
- VAIO Phone Biz
- MouseComputer MADOSMA Q601
- Trinity NuAns NEO
What's new for PC?
- Windows Subsystem for Linux Gains Serial Device Support: Windows COM ports can now be accessed directly from a WSL process!
- You can now hold down the power button on your device for 7 seconds to trigger a bugcheck. This will only work on newer devices that don't uses legacy ACPI power buttons.
- Narrator will work again on this build.
- We fixed the issue causing some apps and games to crash due to a misconfiguration of advertising ID that happened in a prior build.
- We fixed an issue resulting in the Start menu and Action Center having a noticeable framerate drop in their animations on certain devices if transparency was enabled and there were open UWP apps.
- We fixed an issue from the previous build where the Action Center could get into a state where dismissing one notification unexpectedly dismissed multiple.
- We fixed an issue where the Clock and Calendar flyout was unexpectedly missing the agenda integration for some Insiders.
- We fixed an issue from the previous build (Build 16170) resulting in Surface Books unexpectedly doing a disk check after waking from sleep due to it bugchecking during sleep.
- We fixed an issue from the previous build resulting in Win32 app text sometimes not rendering, for example in File Explorer, until logging out and back in.
- We fixed an issue where the Extensions Process was suspended inappropriately during Connected Standby, resulting in Microsoft Edge becoming unresponsive on wake if any extensions had been installed.
What's new for Mobile?
- We have added a new privacy page to the Windows 10 Mobile OOBE experience that allows you to quickly and effectively make common privacy changes while setting up the device. You can read more about our Windows 10 privacy journey here.
- We fixed the issue where the keyboard would sometimes not appear when a text input field is selected in Microsoft Edge. Known issues for Mobile
Windows Central Newsletter
Get the best of Windows Central in your inbox, every day!
Zac Bowden is a Senior Editor at Windows Central. Bringing you exclusive coverage into the world of Windows on PCs, tablets, phones, and more. Also an avid collector of rare Microsoft prototype devices! Keep in touch on Twitter: @zacbowden.
For Insiders who have upgraded from a prior 150xx build to this build, the “Add Bluetooth or other devices” Settings page and the Connect UX page may fail to open
-We fixed an issue resulting in the Start menu and Action Center having a noticeable framerate drop in their animations on certain devices if transparency was enabled and there were open UWP apps.
Anyway, I'm not gonna do Insider builds on the daily driver. So no more Insider for me here... ☹
They need to their safe spacer closet, coloring books and a puppy, maybe Katy Perry can help sooth their trauma.
Well my next phone will be a GPixel or an iPhone with M$ apps that are better supported than native. If W10M' s gonna be abandonware then at least give us the code for the drivers or ability to transform the phone into an Android . I wish W10M all the worst (cause M$ is destroyed such a beautiful phone environment), but I'll stick to it until it dies (cause money). Farewell Windows 10 on what ever mobile. Bye
Quote: "you can't get something, for nothing..." Applies here.
Samsung S8 MS Edition?
Get yourselves a cheap android or a second hand iPhone, and don't panic. It's not dead until they come out and say its dead. Below is the reason she gave for different build numbers. "The biggest difference being that the build number and branch won’t match the builds we will be releasing for PC. This is a result of more work we’re doing to converge code into OneCore – the heart of Windows across PC, tablet, phone, IoT, HoloLens, Xbox and more as we continue to develop new improvements for Windows 10 Mobile and our enterprise customers."
Oh, I forgot....I opted out of Insider Program!