I see on a lot of answers here when people ask about these errors and warnings, the advice is usually that they can be ignored (Googling one of these errors brought me to this exact forum, to which someone else had already asked and the answer was the usual "That can be ignored").
On the face of it, it doesn't seem prudent to ignore anything labeled "Warning" or "Error" (that last one with an ominous looking red icon, no less). If they can in fact be ignored, can the developers not simply label these "Information" instead, and save the "Warning" and "Error" labels for actual warnings and errors?
I learned years ago that in Linux logs, a lot of the "FAILED"-labeled scary looking "errors" are not in fact errors. For example, a particular module may be loaded early on in the boot process (successfully and without issue), then attempted to be loaded again later, which fails (simply because it's already loaded) but it generates a "LOADING FAILED!" error instead of an "Already loaded" notification.
So is that what's going on with these Windows 11 Event Viewer warnings and errors? They're really notifications, not that something went wrong, it just generated that in the log simply because it was too early for that particular thing to happen, it already happened, etc?