How to fix LSA package is not signed as expected event log entries?

That just disables the logging for that event. It doesn't solve the actual problem behind it.

Genuinely interested, why would any business ever start to even imagine that an individual would willingly re-install their OS every 2-3 years

If you are seeing LSA errors for packages negoexts, kerberos, msv1_0, tspkg, pku2u, cloudap, wdigest, schannel, sfapm - it looks like you can ignore those, because they are related to password-based SSO, according to this. These specific warnings (they are not errors in the event viewer!) only indicate that something tried loading one of the affected protocols or it was just the general attempt to load the library. According to MS article, this only blocks SSO, not the whole protocols.

It is clear, that for these particular instances it would warrant Microsoft to write a more appropriate warning text, perhaps also indicating what was calling the library or whether it was a general load of the library during boot-up sequence.

I have not found a way to learn what is actually triggering these libraries/protocols, and what can be done to disable them, if that is safe enough for a particular system (because if they are in use, disabling them may affect other apps).

The most useful and sensible reply in this entire thread.

Thank you

A clean boot produced the same errors, so I decided to restore the desktop to the previous version of Windows 11 Pro. I might try to upgrade next year or wait until I am forced to upgrade.

I have already restored the desktop to the previous verson of Windows 11, but I did save the event logs.