As far as I understand this - yes. But note that this is a Windows component and I don't think I'm super comfortable telling you why it might not be working for you (could be blocked, as you say).
In any case - you should be OK though; the certificate in question has actually been published since sometime in 2024. So your last refresh was after certificate was already out. You can verify by running:
Get-ChildItem -Path Cert:\LocalMachine\Root\ | Where-Object { $_.Thumbprint -eq "DF3C24F9BFD666761B268073FE06D1CC8D4F82A4" }
If you find the rest (like the one in the blog post screenshot) - you are OK as far as this change does (but yes, keep figuring why updating seems to not work is a good idea!)