stdin82

Office 2016/2019 don't have InfoPath or SharePointDesigner apps to exclude you don't need to specify en-us for proofingtools, it's already covered by main product

https://insider.office.com/en-us/releasenotes/pc/slow Office Insider is not open for all like Windows Insider

`RtlGetNtVersionNumbers` (and `RtlGetNtProductType`) are not affected by the manifest thing, and return the correct version or you can directly read KUSER_SHARED_DATA structure for NtMajorVersion, NtMinorVersion, NtProductType and NtBuildNumber (only populated...

@heaths "Update for Windows 10 (KB5001716)" is msi package, and it's using the following for LaunchCondition (both x64 and x86) `VersionNT>=603 AND MsiNTProductType=1 AND NOT CURRENTBUILD="9600" | This application only...

What i ment is that Windows 10 update team is using that LaunchCondition how it's undocumented? that registry value exist since WinXP

> and when I have upgraded a system to the new revoked hashes (which I will need to do carefully and make sure to keep a copy of the revocation...

Maybe the efi files from that iso are not revoked? i checked SHA-256 of bootx64.efi & bootmgfw.efi from `en_windows_8.1_with_update_x64_dvd_6051480.iso`, they are not listed in dbx_info.csv

I see the standard SHA-256 of bootmgfw.efi (both x86/x64) from Windows 8.1 update KB3084905 are listed though, and Get-AppLockerFileInformation result match the listed PE256 Authenticode neither values are listed for...

Doesn't KB5025885 article state that `SKUSiPolicy.p7b` should not be copied to the boot media (ISO, USB, DVD..)?

1607 ISO is the oldest i still keep :grinning: and i did find PE256 hash for `bootx64.efi / bootmgfw.efi / bootmgr.efi` in SKUSiPolicy.xml