Fix developed and shipped in 24.45 enterprise branch (28/03)
Cherry-picked back into 24.40 consumer branch
24.40.0.4 built on 14/04 — carries that fix
This is why 24.40.0.4 postdates 24.45.0.3 despite being a "lower" version.
The .4 suffix signals it wasn't a routine increment - it was a targeted backport to get the fix into Windows Update / Intel channel, since 24.45 is invisible to consumer users.
