Event ID 13 VSS

This is what the error shows
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.
] It is a red flag. not sure if it something to be ignored or not
Lots and lots of yellow flags in System but I do believe they can be ignored
Thanks

So do I ignore the Event ID 13 ?

@man00


I found this...






Also.... make sure you have the latest Intel chipset drivers, using this tool...

I don't look into Event Viewer if my Windows 11 have no problems operating so ignore the event log if you have no problems.

FreeBooter said:

I don't look into Event Viewer if my Windows 11 have no problems operating so ignore the event log if you have no problems.

Click to expand...

Yep, we dont have problems , if you dont see them............ !

In my system, from the beginning on (the system came ready installed from the supplier) there are many warnings and errors in the Event Viewer ('logboeken' in Dutch). Like:
DistributedCOM 10005
Service Control Manager 7001
Service Control Manager 7000
LSA(LsaSrv) 6155
DeviceSetupManager 200, 201, 202
CertificateServicesCIient-CertEnroll 86
Kernel-EventTracing 1, 2, 28

Long ago, in Windows 7 (totally other PC) I tried to avoid some of the errors, by taking measures to be found in the Internet.
I was reasonably succesful as far as Kernel-EventTracing and DistributedCOM were concerned. But after a while such errors came back. Especially at start of the system and after rewaking from sleep state there are many errors and warnings in the log.

That was once used by those 'Microsoft helpdesks' that phoned people to tell them how bad the system was and that they had to install software provided by the 'helpdesk'. The told to look in the log and told them which errors and warnings they had, so that those users would think they were in contact with the real helpdesk. In the end that software was to take over the use of the computer and block it or even steal money via banking accounts.

That's how common those errors are and already a long time I don't look in the log unless my system really is having troubles. When looking there, I know that there are many errors since the beginning of the system and filter out those, just to 'keep' the unusual ones and hopefully be able to search the Internet for known problems showing that error..