Build 14393.103

[Trouble]

Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3176938)
For Windows Insiders on the "Release Preview" ring bumps the build from .82 to .103, which would suggest that we'll be seeing another cumulative update for our Redstone 1, production machines soon.

We have released Cumulative Update (KB3176938) to Windows 10 Insider Preview Build 14393 for PC and Mobile to Windows Insiders in the Slow and Release Preview rings. This will bring the build number to 14393.103. Here are the fixes and improvements for 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.

SOURCE: Feedback / Insider Hub

 

[Tim Locke]

Tuesday perhaps?

 

[Trouble]

Tuesday perhaps?

That seems to be the current arc of updates ...... every Tuesday is Update Tuesday.
Improved reliability of
File Server,
Windows kernel,
Microsoft Component Object Model (COM),
NTFS file system,
graphics,
Windows Shell.
Those are six pretty heavyweight pieces of the pie. Makes you realize the number of moving parts involved and how and even perhaps why some people are experiencing issues while others are not.
There's got to be a level of complexity involved with this process that I can't even begin to understand.
Try though I may to empathize it often looks like they are stumbling over themselves trying to get out of their own way.
I don't think that all the wrinkles were ironed out of 1511 10586,xxx Threshold 2 and now we are dealing with the "Anniversary" update.
IF you ask me, they could have celebrated that "anniversary" a little later and left it for the "insiders" to tinker with a bit longer.