Hello, I shearch for Microsoft-Windows-Internet-Browser-Package~31bf3856ad364e35~amd64~~10.0.14393.693.cab And for Microsoft-Windows-Internet-Browser-Package~31bf3856ad364e35~amd64~fr-FR~10.0.14393.693.cab Or any way to install Edge 14393.693 on Server 2016 with KB3213986.
Weird that we have not seen a 2.4 key yet. Wondering if this means that we are not seeing 2016 servers rolling out to business's. Or are there just less people getting the key from the server nowadays? I am sort of guessing servers are mostly vmware hosts, and the clients are using VLK. All previous versions were leaked much quicker.
I found the only reliable update mechanism from WSUS for Windows 2016 and 10 1607 to use the full file and WUDO configured to Bypass (100 decimal). I don't think the client was fixed although this has been promised for a while on various Microsoft blogs. Only 1607 builds are affected by this issue.
Code: File name:SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_ChnSimp_-3_MLF_X21-30349.iso SHA1:D0C55A029DC7FD986B033E6B66DD73DE7E18A9CE ed2k://|file|SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_ChnSimp_-3_MLF_X21-30349.ISO|6201106432|CF460F6D875B3FA0C215F2F85B5C4392|/
Yes it works on Windows 10 v1607, and require November (or December) cumulative update to revert the policy, disable it (or not configured), then lauch admin cmd: Code: net stop usosvc net stop wuauserv UsoClient.exe StartScan