It's not same update file, the update is distributed on several files to reduce load (on both msft servers and user WU client) those files are used by WU/WSUS to utilize express-download feature which reduce the download size for client you should not use these files, you only need the complete compressed cab file Code: windows10.0-kb3176934-x64_5eedcc98de283d69a008c7cfe63df0d5a7bedb8c.cab
All latest 1607 updates (including .cab) now added to review. Sorry guys.. Neighbour severed my broadband and phone lines (so only intermittent access) ISP (Virgin) has no idea when they will be able to resolve the issue due to cable congestion.. so repair suspended indefinitely.
Looks like there's a 3176938 update out now (Release preview only?) (Following the earlier 3176934 and 3176932 )
x86 - _ttp://download.windowsupdate.com/d/msdownload/update/software/crup/2016/08/windows10.0-kb3176938-x86_fcce9f1cfc3c8a17af535796f49c44e66baaace8.cab
Warning! KB3176938 (14393.103) breaks something in network security. After installing it I can no longer edit Group Policy, and every remote desktop connection which I had previously saved credentials for now forces typing the password every time. There are probably other things not working now but I haven't found them yet. Even better, after uninstalling the update and being back at 14393.82, this problem is still there! I wonder what it's changing that survives an uninstall.
I slipstreamed KB3176936 and KB3176938 into my iso then did a clean install everything is working over here. And as a matter of fact the OS feels better to me also.
gpedit.msc works here although if it's a specific policy that can't be edited that's probably a bug then. Also noticed that some of the System32 and SysWoW64 files that had previously been updated to .82 are back to .0 now though the .82 and .103 versions are still in the WinSxS folder or what that repository was called so it's probably nothing, checkhealth and restorehealth found nothing either though dism complained about some missing file when I first ran the clean-up resetbase command (Did the same with .82 so I've been running the resethealth command afterwards for both these updates.) although it seems to be a common error in various versions of Win10 from what I found via searching around and the cbs and dism .log files just seem to point to some "null" thing so it seems harmless and running the cleanup one more time succeeds without error. That said these are preview updates not 100% ready for public full release. (Not sure if they're even available via the fast or slow ring, I guess fast is out entirely as that's going to move you to a very early build of RS2 come to think of it and slow-ring might be getting prepared too if the current build doesn't have too many known issues even if it's a pretty early RS2 build as such seeing how MS appears to have settled for more frequent releases to insiders.) EDIT: [h=2]Windows 10 build 14393.103 Fixes & Improvements[/h] 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. Might include some of the earlier cumulative update fixes as I think I've seen some of these notes already, probably also unlisted fixes as usual.
This is on a domain with 2012R2 domain controllers. I suspect that it has something to do with too much NTLM on my network and how to make it more secure. Running gpupdate now produces errors and I notice that I cannot navigate anymore to \\mydomain.local\SYSVOL as it says network access is denied.
It's rolled in phases, newer systems get it first, and specially the system that don't block telemetry or disable "Microsoft Compatibility Appraiser" task You could trick WU to offer it by this registry Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade] "AllowKMSUpgrade"=dword:00000001 "AllowOSUpgrade"=dword:00000001 "PermittedOSBuilds"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\steam] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Appraiser\GWX] "GStatus"="2" "SdbEntries"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\RS1_reduced] "Free"="32to64" "Bios"="2015" "UpgEx"="Green" "ISVM"="0" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability] "EnablePreviewBuilds"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings] "DeferUpgrade"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] "DeferUpgrade"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\Update] "RequireDeferUpgrade"=- [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Update] "RequireDeferUpgrade"=- [HKEY_LOCAL_MACHINE\SYSTEM\setup] "UninstallActive"=- [HKEY_LOCAL_MACHINE\SYSTEM\Setup\Mosetup\Tracking] "RollbackCount"=- [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade\Rollback\10.0.14393.0] [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability\RecoveredFrom]
3176938 does contain the updated contents of 3176937. They're bumped to version .103 in 3176938 (.100 in 3176937). But there are some language resource files that were in the previous CU (3176934) that are not present in 3176938. Not sure why they are not included in the new one, since I thought these were cumulative...