Possible it was also (2023-05 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5026372)).
That's exactly what it was. Code integrity policies were updated, and EAC is either incompatible with core isolation features or deemed vulnerable to ROP exploits, so Windows prevents the service from launching. (Note: It's not just EAC ... several other anti-cheat services seem to be affected too.)
We're stuck with limited options on this one ...
- wait for Epic to roll out an update to EAC that Microsoft deems sufficiently secure,
- roll back that cumulative update (miss out on included features, rely on potentially outdated security definitions), or
- disable security features (namely hardware-enforced stack protection).
Never thrilled with rolling back updates or disabling security, but given the lack of public comment so far from Epic, I'm not super hopeful it'll be a short wait before we get the proper fix. I'm probably going to end up taking the third bullet over missing my weekend gaming.