Yeah, the BitLocker issue isn't fixed with this new update. However, Microsoft has finally acknowledged it and are "working to isolate and confirm the BitLocker issue".
I'm not quite sure how to use these. They don't seem to be integratable, and if you copy the contents over the old ones it gives setup errors. I think they are intended for download only.
I haven't tried these particular ones, yet. I'm momentarily quite buisy creating all 1511 svf.sfx patches.
The difference between the previous cumulative (3118754) and the new one (3120677) is the addition of the following components (all are ver 10.0.10586.14): amd64_microsoft-appmodel-exec-events (Microsoft-Windows-AppModelExecEvents.dll) amd64_microsoft-windows-advertisingid amd64_microsoft-windows-deviceaccess (AppPrivacy.admx, dabmigplugin.dll, deviceaccess.dll) amd64_microsoft-windows-modernexecserver (modernexecserver.dll) amd64_microsoft-windows-web-app-host (WWAHost.exe) wow64_microsoft-windows-deviceaccess (dabmigplugin.dll, deviceaccess.dll) wow64_microsoft-windows-web-app-host (WWAHost.exe) and amd64_microsoft-windows-coreos-revision has changed from 10.0.10586.11 to 10.0.10586.14
Oops, didn't catch that. What I ended up doing was delete the "Final" key and then recreate it, this sets new permissions based on the "ADOVMPPackage" key. It works. Code: reg load HKLM\temp W:\windows\system32\config\system reg delete HKLM\temp\ControlSet001\Services\ADOVMPPackage\Final /f reg add HKLM\temp\ControlSet001\Services\ADOVMPPackage\Final /v ActivationEnabled /t REG_DWORD /d 2 /f reg unload HKLM\temp