@joshbressers there's conflation between fixing the bug (long ago) and rolling out revocations, which has been intentionally delayed to try to avoid this. Too early to be sure, but MS has tried to detect dual-boot and let the Linux side do the revocation. My suspicion is we're seeing Linux installs that haven't been updated in 2+ years interacting with a bug in MS's dual boot detection (which they ran by us at a high level and we thought would work.)