No need for more testing, Enthousiast- you are 100% correct. (I just learned about this.) Regardless of what updates are integrated (including the cumulative one), updates classified as OOBE will still be downloaded and installed during OOBE even if the updates are superseded. I learned something, so thanks Enthousiast (and to abbodi1406 for the info above).
Not tested, but it should change CurrentControlSet to ControlSet001 the trick is in setting the permissions, not just changing the key value unless you upgrade from Win7/Win8.1, you don't need them
Here's what I'm trying, my script contains: Code: reg load HKLM\temp W:\windows\system32\config\system reg add HKLM\temp\ControlSet001\Services\ADOVMPPackage\Final /v ActivationEnabled /t REG_DWORD /d 2 /f SetACL.exe -on "HKLM\temp\ControlSet001\Services\ADOVMPPackage\Final" -ot reg -actn restore -bckp .\ADOVMPPackage.txt reg unload HKLM\temp and my ADOVMPPackage.txt contains: Code: "HKLM\temp\ControlSet001\Services\ADOVMPPackage\Final",4,"O:SYG:SYD:AI(A;CI;CCDCLCSWRPRC;;;IU)(A;CI;CCDCLCSWRPRC;;;SY)(A;CI;CCDCLCSWRPRC;;;BA)(A;CIID;KR;;;BU)(A;CIID;KA;;;BA)(A;CIID;KA;;;SY)(A;CIIOID;KA;;;CO)(A;CIID;KR;;;AC)" Since I'm running in PE, I don't need a super command prompt (and I already know I can modify the values).
Same here. I thought that maybe it recognizes clean installs vs. upgrades and then doesn't show the update for clean installs as the only change is related to the reset privacy settings if upgrading. However, even after uninstalling the previous cumulative update (KB3118754), it still finds KB3118754 and reinstalls it, and not the new one. I'm sure someone will post direct links to the update soon.
Nothing Bitlocker related updated in the cumulative App model execution (WinRT stuff) and DeviceAccess policy