I agree that this looks like a 3rd party issue. They claimed that KB5044284 was the update, but others have noted that after installing that update, they had t

I agree that this looks like a 3rd party issue. They claimed that KB5044284 was the update, but others have noted that after installing that update, they had the option to upgrade to 2025 but it didn't happen automatically - seems the 3rd party RMM somehow pushed a command to start the upgrade. Honestly, I guess since it's an SMB it might make sense that they aren't able to test all patches before applying them in production, but you'd hope they'd delay the installation for a few days to let others catch major issues.