Hello Dylanger Shots,
Thanks for circling back with the fix. It's really useful that you laid out what didn't work too.
The reason the Update Catalog route worked is that 0x80073712 usually means a piece of the servicing/component store is missing or out of sync, and Windows Update keeps tripping on it. Grabbing the standalone .msu and running it directly sidesteps that whole pipeline and just applies the package — which is also why a second run can push it through after the first one looks like it failed.
I appreciate you sharing the resolution and the direct link — this is a clean, repeatable fix, and it'll save the next person hitting 0x80073712 on KB5089549 a lot of the same dead ends you already ruled out.