Microsoft today released a new cumulative update for Windows 10, which brings the build number to 14393.479. KB3201845 was originally offered to the Release Preview ring of the Insider Preview on November 29 for both PC and Mobile, but phones aren't seeing an update today.
The timing for today's update is certainly odd. Next Tuesday is Patch Tuesday, which is the day that cumulative updates are normally released every month. There's also no changelog listed on the Windows 10 Update History page, which normally gets updated as soon as the build is released to the Production ring (non-Insiders).
Windows Central has come up with a changelog though. Here's what's new:
Improved the reliability of mobile device management (MDM) disenrollment, Distributed Component Object Model (DCOM), Peripheral Component Interface and PowerShell.
Addressed issue that causes excessive battery drain if you have a Chinese Input Method Editor installed and use Windows Hello to log in.
Addressed issue with OLE drag and drop that prevents users from downloading a SharePoint document library as a file.
Addressed issue with Super Floppy-formatted fixed media devices that are not recognized by Windows 10 Anniversary Update or accessible in Windows Explorer.
Addressed issue that causes the System Center Configuration Manager (SCCM) client to fail installation when a device is re-imaged using the SCCM task sequence.
Addressed issue that causes the loss of optional component (OC) state information, including all Hyper-V virtual machines, after upgrade.
Addressed issue that causes Windows Explorer to display information that's inconsistent with what's stored on the Floppy disk.
Addressed issue that, after connecting a shared CD/DVD-hosted drive with no media inserted, causes some of the commands, like DIR and NET USE, to hang.
Addressed issue where customers cannot use directory cache sizes greater than 64 KB.
Addressed issue where Windows Explorer sometimes does not prompt for credentials when a user logs on using a Microsoft account.
Addressed additional issues with application compatibility and Internet Explorer
It's entirely possible that build 14393.479 for Windows 10 Mobile won't arrive in the Production ring at all. Microsoft said that the update broke tap-to-pay on the three phones that actually support it, and that the issue would be fixed in the next Release Preview build; however, there hasn't been one just yet.
15 Comments - Add comment