Insiders on the Slow and Release Preview rings found a cumulative update waiting for them today, specifically Windows 10 build 14393.103 for PC and Mobile. At the time, there wasn't a changelog available; however, one has since been published.
As you might expect, there aren't any new features to be seen in a cumulative update; however, there are a number of fixes and improvements. Here's what's new in Windows 10 build 14393.103:
Improved reliability of the Windows Ink Workspace, Microsoft Edge, File Server, Windows kernel, Microsoft Component Object Model (COM), Cluster Health Service, Hyper-V, Multi-Factor Authentication (MFA), NTFS file system, PowerShell, Internet Explorer, facial recognition, graphics, Microsoft Store and Windows Shell.
Improved performance for the speed of purchasing Store apps.
Improved battery life of wearable devices (such as the Microsoft Band) while Bluetooth is connected and idle.
Improved compatibility of using Xbox One controllers with various games.
Addressed issue with incorrect character mapping between Japanese and Unicode for the question mark (?) symbol.
Addressed issue that prevents the download and initialization of .NET objects in Internet Explorer.
Improved support for new near-field communication (NFC) chips for Windows 10 Mobile.
Addressed issue with game or app audio not resuming after ending a call on Windows 10 Mobile.
Addressed additional issues with compatibility, Remote Desktop, BitLocker, PowerShell, Direct3D, networking policies, Dynamic Access Control (DAC) rules, Microsoft Edge, Connected Standby, mobile device management (MDM), printing, Fingerprint logon and Cortana.
The notes list "PowerShell" in passing, although the previous update on PCs broke DSC. Microsoft has promised a fix on August 30, and it's unknown whether this is a preview of the upcoming update.
There are also a number of other issues in the Anniversary Update that the changelog doesn't call out. Users are finding that plugging in a Kindle causes Windows 10 to crash, and millions of webcams are broken. Clearly, Microsoft has a lot to fix over the next few updates.
4 Comments - Add comment