The same happens to me with both MP and MCE. Edit: I figured it was a decoder problem, I force MCE to switch from MS decoder to LAV (I used an utility for MCE for Win7) and now it works perfectly without having to modify any files. The name of the utility is MCDU, is a 32kb app, just google it. Edit2: On the thread for MCE on Win10 a user have found another solution, check that thread. It involves changing to a previous version a file on System32.
Update for Windows 10 Version 1511 (KB3150513): Code: hxxp://download.windowsupdate.com/c/msdownload/update/software/updt/2017/03/windows10.0-kb3150513-x86_ee2c4f232513d65a33b4f353aaf713134a8b6cab.msu hxxp://download.windowsupdate.com/c/msdownload/update/software/updt/2017/03/windows10.0-kb3150513-x64_48c5fb66ffab675af4790462a53d866203012c19.msu Update for Windows 10 Version 1607 (KB3150513): Code: hxxp://download.windowsupdate.com/d/msdownload/update/software/updt/2017/03/windows10.0-kb3150513-x86_1dfeeaa6287ced8ac348d34c93363fee99197238.msu hxxp://download.windowsupdate.com/d/msdownload/update/software/updt/2017/03/windows10.0-kb3150513-x64_c89b98dc5afed3046857165840bd2e52a5dc0d8a.msu Note. Replace xx with tt at given links.. Greets smiler10
Thanks smiler10 for posting those updated versions. For anybody wondering, the new one he posted for 1511 is version 10586.840; previous was 10586.681. The new one supersedes the old version of KB3150513. Actually, that old one probably wasn't needed in the repo list since a newer version (10586.839) of the component contained in it (microsoft-windows-c..-appraiser-hwcompat) is contained in the CU KB4013198. For 1607, the version of the component is 14393.967; old ver was 14393.953. Since the old component is contained in the CU (KB4013429), it's not superseded and this new KB3150513 is needed additionally to have the latest versions. Probably next CU releases will supersede out these new KB3150513 versions. But for now they're needed.
Right- the build number of the component contained in KB3150513 is .967. The overall Windows build number that's shown in the BuildLabEx reg key and through winver relates to the version of microsoft-windows-os-kernel component (ntoskrnl.exe) and it remains .953 since it wasn't updated.
so far no drama on my server 2016 datacenter laptops; holding off updating my spare win 10 laptop since december 2016 patch tuesday as it is so close to creators edition; will wait for rtm and then go whole hog and upgrade it to that rtm instead of waste bandwidth on bloated patches as that will be a new build anyways and probably have a small cumulative update soon after
do you remember how soon we were able to get our hands on rs1 right after the final insider build? somewhat i can't recall. if its a week i wouldnt mind waiting. i do feel the next build is either the last or the final and im counting on this.
What bloated updates you're referring to. Tested a fresh 14393 Vanilla Install yesterday and WU only offered current Servicing Stack, CU and Flash Security updates .
I am using LTSB 2016, and I got this "update" KB3150513 yesterday evening. Is that normal ? Seems related to telemetry ? KB3150513