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

I have BSOD shortly after receiving these messages. I turned off LSA and TMP module.

I have Professional, and I get the warnings.

I tried your registry change and it did stop the logging it the warnings.

There shouldn't be innocuous warnings logged, and why they aren't removed is a mystery.

"Besides, what if you hide the event and then an actual issue occurs that can be identify by the log entry that you've silenced? Will you suggest Windows reinstall then?"

There will be other events that will tie into it if there is an ACUTAL Issue.. and besides it not that hard to turn back on either (same as I posted with using a 1 instead of a 0)

If your computer won't even boot or is unusable and you need to turn that event back on, then I'm sorry you have bigger fish to fry in that case and turning it back on again isn't going to help you so yes, a re-install is probably going to fix it.

Your comment/scenario is just hyperbole at best.

Hm... That's an interesting question. Since you are experiencing this on boot, and RunAsPPLBoot is a setting, that enables LSA during boot, it theoretically can be interfering. I doubt it's the case, unless the scanner device uses some weird (or possibly just outdated) protocol or whatever, but this is a possibility. You can try setting just RunAsPPLBoot or both of the settings to 0 and see if that changes anything. You won't risk anything by doing that, if you revert the settings back afterwards. If your assumption is proven correct, I would consider contacting Microsoft's support to report this as a potential bug.

Could it be related to 2 missing entries in the registry of Windows that you should add?

under

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

DWORD:

RunAsPPL value:2

and

DWORD:

RunAsPPLBoot value:2