Level,Date and Time,Source,Event ID,Task Category

Critical,19/10/2022 11:11:52,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do

Error,19/10/2022 11:12:00,EventLog,6008,None,The previous system shutdown at 10:24:57 AM on 10/19/2022 was unexpect
Critical,19/10/2022 10:24:49,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,19/10/2022 10:24:49,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,19/10/2022 10:24:57,EventLog,6008,None,The previous system shutdown at 10:20:05 AM on 10/19/2022 was unexpect
Critical,19/10/2022 09:47:23,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,19/10/2022 09:47:23,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,19/10/2022 09:47:32,EventLog,6008,None,The previous system shutdown at 9:44:20 AM on 10/19/2022 was unexpecte
Critical,19/10/2022 09:44:13,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,19/10/2022 09:44:13,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,19/10/2022 09:44:20,EventLog,6008,None,The previous system shutdown at 9:41:50 AM on 10/19/2022 was unexpecte
Error,19/10/2022 09:09:19,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:09:19,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:07:02,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:07:02,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:05:06,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:05:06,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:03:32,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:02:51,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:02:51,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:02:20,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:02:20,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:01:59,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:01:59,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:01:45,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:01:36,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 09:01:36,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,19/10/2022 08:31:58,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/10/2022 23:37:51,Microsoft-Windows-DistributedCOM,10010,None,The server Microsoft.AAD.BrokerPlugin_1000.19
Error,18/10/2022 17:02:57,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Critical,17/10/2022 14:48:43,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,17/10/2022 14:48:52,EventLog,6008,None,The previous system shutdown at 2:14:00 PM on 10/17/2022 was unexpecte
Error,17/10/2022 13:23:20,Microsoft-Windows-Eventlog,30,Service startup,"The event logging service encountered an error (
Error,17/10/2022 13:21:59,Service Control Manager,7000,None,"The ClickToRunSvc service failed to start due to the following
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:59,Service Control Manager,7000,None,"The wampstackMariaDB service failed to start due to the fol
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:59,Service Control Manager,7000,None,"The MYSQL_FTM service failed to start due to the following e
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7001,None,"The AppXSvc service depends on the StateRepository service
The operation completed successfully."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The wampstackApache service failed to start due to the follo
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The ASUSLinkRemote service failed to start due to the follow
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The TurboVPNService service failed to start due to the follow
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The WerSvc service was unable to log on as NT AUTHORITY\S
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The WMIRegistrationService service failed to start due to the
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The nlsX86cc service failed to start due to the following erro
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The ASUSSystemAnalysis service failed to start due to the fol
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The AsusAppService service failed to start due to the followin
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The McAfee WebAdvisor service failed to start due to the fol
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The ASUSLinkNear service failed to start due to the following
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The RtkAudioUniversalService service failed to start due to th
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The ASUSSwitch service failed to start due to the following e
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The ASUSSystemDiagnosis service failed to start due to the f
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The ICEsoundService service failed to start due to the follow
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The cplspcon service failed to start due to the following erro
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The esifsvc service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The EpsonScanSvc service failed to start due to the following
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The ASUSOptimization service failed to start due to the follo
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The NitroDriverReadSpool9 service failed to start due to the
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The LanmanServer service failed to start due to the following
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The LanmanServer service was unable to log on as NT AUTHO
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7001,None,"The RasMan service depends on the SstpSvc service which fa
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The TapiSrv service failed to start due to the following error:
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The TapiSrv service was unable to log on as NT AUTHORITY\N
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The WpnService service failed to start due to the following e
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The TrkWks service failed to start due to the following error:
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The WpnService service was unable to log on as NT AUTHOR
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The WinDefend service failed to start due to the following er
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The SstpSvc service failed to start due to the following error:
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The stisvc service failed to start due to the following error:
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The TrkWks service was unable to log on as NT AUTHORITY\S
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The WinDefend service was unable to log on as NT AUTHORI
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The Winmgmt service was unable to log on as NT AUTHORIT
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The SstpSvc service was unable to log on as NT Authority\Loc
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The stisvc service was unable to log on as NT Authority\Loca
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7001,None,"The jhi_service service depends on the iphlpsvc service whic
The dependency service or group failed to start."
Error,17/10/2022 13:21:57,Service Control Manager,7001,None,"The iphlpsvc service depends on the Winmgmt service which
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The DPS service failed to start due to the following error:
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The Winmgmt service was unable to log on as NT AUTHORIT
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The DiagTrack service failed to start due to the following erro
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The DPS service was unable to log on as NT AUTHORITY\Loca
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The CryptSvc service failed to start due to the following erro
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The CryptSvc service was unable to log on as NT Authority\N
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The DiagTrack service was unable to log on as NT AUTHORIT
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The LanmanWorkstation service failed to start due to the fol
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The LanmanWorkstation service was unable to log on as NT
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7001,None,"The mpssvc service depends on the BFE service which failed
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The BFE service failed to start due to the following error:
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The BFE service was unable to log on as NT AUTHORITY\Loca
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The DpHost service failed to start due to the following error:
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The DpHost service was unable to log on as NT AUTHORITY\S
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The Spooler service failed to start due to the following error:
The service did not start due to a logon failure."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The Spooler service was unable to log on as NT AUTHORITY\
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,17/10/2022 13:21:57,Service Control Manager,7000,None,"The FA_Scheduler service failed to start due to the following
The service did not respond to the start or control request in a timely fashion."
Error,17/10/2022 13:21:57,Service Control Manager,7038,None,"The ShellHWDetection service was unable to log on as NT AU
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Critical,17/10/2022 13:21:20,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,17/10/2022 13:21:20,volmgr,46,None,Crash dump initialization failed!
Error,17/10/2022 13:21:56,EventLog,6008,None,The previous system shutdown at 1:07:23 PM on 10/17/2022 was unexpecte
Error,15/10/2022 18:57:18,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 18:57:27,EventLog,6008,None,The previous system shutdown at 6:50:03 PM on 10/15/2022 was unexpecte
Error,15/10/2022 18:49:54,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 18:50:03,EventLog,6008,None,The previous system shutdown at 6:16:40 PM on 10/15/2022 was unexpecte
Error,15/10/2022 17:26:31,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 17:26:40,EventLog,6008,None,The previous system shutdown at 5:15:40 PM on 10/15/2022 was unexpecte
Error,15/10/2022 17:15:31,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 17:15:40,EventLog,6008,None,The previous system shutdown at 5:03:54 PM on 10/15/2022 was unexpecte
Error,15/10/2022 16:32:36,EventLog,6008,None,The previous system shutdown at 3:27:05 PM on 10/15/2022 was unexpecte
Error,15/10/2022 15:26:57,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 15:27:05,EventLog,6008,None,The previous system shutdown at 3:24:07 PM on 10/15/2022 was unexpecte
Error,15/10/2022 15:23:58,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 15:24:07,EventLog,6008,None,The previous system shutdown at 3:08:58 PM on 10/15/2022 was unexpecte
Error,15/10/2022 15:08:48,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 15:08:58,EventLog,6008,None,The previous system shutdown at 2:44:47 PM on 10/15/2022 was unexpecte
Error,15/10/2022 13:24:37,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 13:24:47,EventLog,6008,None,The previous system shutdown at 1:10:21 PM on 10/15/2022 was unexpecte
Error,15/10/2022 13:10:12,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 13:10:21,EventLog,6008,None,The previous system shutdown at 1:00:45 PM on 10/15/2022 was unexpecte
Critical,15/10/2022 12:10:38,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,15/10/2022 12:10:38,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 12:10:45,EventLog,6008,None,The previous system shutdown at 12:05:02 PM on 10/15/2022 was unexpect
Error,15/10/2022 10:24:52,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,15/10/2022 10:25:01,EventLog,6008,None,The previous system shutdown at 10:19:17 AM on 10/15/2022 was unexpect
Error,14/10/2022 15:54:18,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,14/10/2022 15:33:35,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,14/10/2022 15:33:43,EventLog,6008,None,The previous system shutdown at 3:07:28 PM on 10/14/2022 was unexpecte
Error,14/10/2022 15:07:39,Service Control Manager,7031,None,The ASUS System Analysis service terminated unexpectedly.
Error,14/10/2022 15:07:19,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,14/10/2022 15:07:28,EventLog,6008,None,The previous system shutdown at 2:58:27 PM on 10/14/2022 was unexpecte
Error,14/10/2022 14:58:18,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,14/10/2022 14:58:27,EventLog,6008,None,The previous system shutdown at 2:54:37 PM on 10/14/2022 was unexpecte
Error,14/10/2022 14:54:29,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,14/10/2022 14:54:37,EventLog,6008,None,The previous system shutdown at 2:52:03 PM on 10/14/2022 was unexpecte
Error,14/10/2022 14:47:03,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,14/10/2022 14:47:12,EventLog,6008,None,The previous system shutdown at 2:42:44 PM on 10/14/2022 was unexpecte
Error,14/10/2022 14:42:35,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,14/10/2022 14:42:44,EventLog,6008,None,The previous system shutdown at 3:11:14 PM on 10/13/2022 was unexpecte
Error,13/10/2022 13:46:33,EventLog,6008,None,The previous system shutdown at 1:36:50 PM on 10/13/2022 was unexpecte
Error,13/10/2022 13:29:52,volmgr,46,None,Crash dump initialization failed!
Error,13/10/2022 13:30:04,EventLog,6008,None,The previous system shutdown at 1:02:16 PM on 10/13/2022 was unexpecte
Error,13/10/2022 12:37:07,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,13/10/2022 12:37:16,EventLog,6008,None,The previous system shutdown at 12:33:38 PM on 10/13/2022 was unexpect
Error,13/10/2022 12:33:30,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,13/10/2022 12:33:38,EventLog,6008,None,The previous system shutdown at 12:27:56 PM on 10/13/2022 was unexpect
Error,13/10/2022 12:27:48,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,13/10/2022 12:27:56,EventLog,6008,None,The previous system shutdown at 12:23:40 PM on 10/13/2022 was unexpect
Error,13/10/2022 12:23:32,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,13/10/2022 12:23:40,EventLog,6008,None,The previous system shutdown at 12:19:54 PM on 10/13/2022 was unexpect
Error,13/10/2022 12:19:43,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,13/10/2022 12:19:54,EventLog,6008,None,The previous system shutdown at 12:01:33 PM on 10/13/2022 was unexpect
Error,13/10/2022 08:22:24,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,13/10/2022 08:21:05,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,13/10/2022 08:21:04,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,13/10/2022 08:20:56,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,12/10/2022 19:37:33,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,12/10/2022 19:37:24,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,12/10/2022 19:37:24,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,12/10/2022 19:37:23,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,12/10/2022 09:14:50,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,12/10/2022 09:14:42,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,12/10/2022 09:05:40,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,12/10/2022 09:05:40,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,12/10/2022 09:01:49,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,12/10/2022 09:01:49,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,12/10/2022 09:01:44,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,12/10/2022 09:01:44,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,11/10/2022 16:21:14,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,11/10/2022 16:21:05,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,11/10/2022 16:21:04,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,10/10/2022 17:07:10,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,10/10/2022 17:07:09,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,09/10/2022 21:20:58,Microsoft-Windows-DistributedCOM,10010,None,The server {995C996E-D918-4A8C-A302-45719A
Error,07/10/2022 19:02:50,Microsoft-Windows-DistributedCOM,10010,None,The server {995C996E-D918-4A8C-A302-45719A
Error,07/10/2022 16:21:52,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,07/10/2022 10:14:09,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,06/10/2022 12:31:20,disk,11,None,The driver detected a controller error on \Device\Harddisk2\DR6.
Error,04/10/2022 01:07:31,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:31,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:31,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:31,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:31,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:31,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/10/2022 01:07:29,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,03/10/2022 17:26:30,Microsoft-Windows-DistributedCOM,10010,None,The server {A463FCB9-6B1C-4E0D-A80B-A2CA79
Error,03/10/2022 17:26:30,Microsoft-Windows-DistributedCOM,10010,None,The server {A463FCB9-6B1C-4E0D-A80B-A2CA79
Error,03/10/2022 17:25:38,Microsoft-Windows-DistributedCOM,10010,None,The server {A463FCB9-6B1C-4E0D-A80B-A2CA79
Error,03/10/2022 17:25:37,Microsoft-Windows-DistributedCOM,10010,None,The server {A463FCB9-6B1C-4E0D-A80B-A2CA79
Error,03/10/2022 17:25:37,Microsoft-Windows-DistributedCOM,10010,None,The server {A463FCB9-6B1C-4E0D-A80B-A2CA79
Error,03/10/2022 17:25:37,Microsoft-Windows-DistributedCOM,10010,None,The server {A463FCB9-6B1C-4E0D-A80B-A2CA79
Error,03/10/2022 13:22:57,Microsoft-Windows-DistributedCOM,10010,None,The server {AB93B6F1-BE76-4185-A488-A9001B
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:56,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 13:22:54,Microsoft-Windows-DistributedCOM,10010,None,The server {D63B10C5-BB46-4990-A94F-E40B9D
Critical,03/10/2022 13:22:00,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,03/10/2022 13:22:08,EventLog,6008,None,The previous system shutdown at 1:18:19 PM on 10/3/2022 was unexpected
Error,03/10/2022 13:19:51,Microsoft-Windows-DistributedCOM,10010,None,The server {A463FCB9-6B1C-4E0D-A80B-A2CA79
Error,03/10/2022 13:19:50,Microsoft-Windows-DistributedCOM,10010,None,The server {A463FCB9-6B1C-4E0D-A80B-A2CA79
Critical,03/10/2022 10:00:37,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,03/10/2022 10:00:34,Microsoft-Windows-Kernel-Boot,29,None,Windows failed fast startup with error status 0xC00000D
Error,03/10/2022 10:00:43,EventLog,6008,None,The previous system shutdown at 9:53:44 AM on 10/3/2022 was unexpected
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:03,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,03/10/2022 09:44:02,Microsoft-Windows-DistributedCOM,10010,None,The server {AB8902B4-09CA-4BB6-B78D-A8F590
Error,01/10/2022 20:32:47,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,01/10/2022 20:30:22,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,30/09/2022 17:09:09,disk,11,None,The driver detected a controller error on \Device\Harddisk2\DR3.
Error,30/09/2022 15:11:52,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,30/09/2022 15:12:05,EventLog,6008,None,The previous system shutdown at 12:14:42 PM on 9/30/2022 was unexpecte
Error,30/09/2022 08:07:36,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,29/09/2022 22:51:25,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,29/09/2022 22:51:25,Microsoft-Windows-DistributedCOM,10010,None,The server Microsoft.AAD.BrokerPlugin_1000.19
Error,29/09/2022 16:47:02,Microsoft-Windows-DistributedCOM,10010,None,The server {9BA05972-F6A8-11CF-A442-00A0C9
Error,29/09/2022 11:17:37,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,27/09/2022 16:55:56,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,27/09/2022 12:08:30,Volsnap,36,None,The shadow copies of volume C: were aborted because the shadow copy storage
Error,27/09/2022 09:21:32,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,21/09/2022 17:47:59,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,20/09/2022 15:39:32,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,19/09/2022 08:09:03,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,16/09/2022 18:35:59,Microsoft-Windows-DistributedCOM,10010,None,The server {59E5039B-6524-481C-A78C-E680D7
Error,15/09/2022 22:13:02,disk,11,None,The driver detected a controller error on \Device\Harddisk2\DR20.
Error,14/09/2022 08:28:32,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,13/09/2022 07:40:55,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,12/09/2022 17:53:57,Microsoft-Windows-DistributedCOM,10010,None,The server B9ECED6F.ASUSPCAssistant_3.1.5.0_
Error,12/09/2022 09:23:24,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,10/09/2022 23:36:34,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,10/09/2022 23:36:34,Microsoft-Windows-DistributedCOM,10010,None,The server Microsoft.AAD.BrokerPlugin_1000.19
Critical,07/09/2022 08:37:37,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,07/09/2022 08:36:42,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,07/09/2022 08:36:54,EventLog,6008,None,The previous system shutdown at 9:31:46 PM on 9/6/2022 was unexpected.
Error,06/09/2022 20:53:39,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:53:39,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:48:33,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:48:33,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:44:26,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:44:26,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:41:08,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:41:08,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:38:22,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:38:22,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:36:23,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:35:13,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:35:13,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:34:39,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:34:39,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:34:10,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:34:10,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:33:45,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:33:45,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:33:21,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:33:21,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:33:02,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:33:02,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:32:48,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:32:48,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:32:38,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,06/09/2022 20:32:38,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 21:21:16,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:16,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:16,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:16,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:16,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:16,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:16,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:16,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:16,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:15,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:14,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:14,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,05/09/2022 21:21:14,Microsoft-Windows-DistributedCOM,10010,None,The server Microsoft.AAD.BrokerPlugin_1000.19
Error,05/09/2022 20:30:29,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 20:30:29,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 20:30:03,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 20:30:03,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 20:29:47,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 20:29:47,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 20:29:32,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 20:29:32,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 20:29:25,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,05/09/2022 13:03:30,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,04/09/2022 16:34:46,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:46,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:45,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:44,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,04/09/2022 16:34:44,Microsoft-Windows-DistributedCOM,10010,None,The server Microsoft.AAD.BrokerPlugin_1000.19
Error,01/09/2022 20:22:20,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:22:10,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:59,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:54,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:54,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:51,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:49,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:41,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:41,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:41,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:41,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:41,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:41,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:39,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 20:21:39,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,01/09/2022 08:06:29,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,31/08/2022 18:18:56,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:56,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:56,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:56,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:56,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:56,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:56,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:56,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 18:18:55,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,31/08/2022 11:59:09,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,31/08/2022 09:57:41,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,30/08/2022 17:55:41,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,29/08/2022 08:00:38,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,26/08/2022 20:10:10,Microsoft-Windows-DistributedCOM,10010,None,The server {FD06603A-2BDF-4BB1-B7DF-5DC68F
Error,26/08/2022 13:34:54,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,26/08/2022 13:25:51,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,26/08/2022 13:21:24,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,26/08/2022 13:19:56,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,26/08/2022 13:19:50,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,23/08/2022 23:20:01,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,23/08/2022 23:19:51,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,23/08/2022 23:19:41,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,23/08/2022 23:19:34,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,23/08/2022 23:19:34,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,23/08/2022 23:19:31,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,23/08/2022 12:24:10,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,23/08/2022 12:24:10,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,23/08/2022 11:48:30,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,21/08/2022 00:19:12,Microsoft-Windows-DistributedCOM,10010,None,The server {9BA05972-F6A8-11CF-A442-00A0C9
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:24,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:23,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 17:02:23,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,18/08/2022 14:04:43,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,18/08/2022 08:23:42,EventLog,6008,None,The previous system shutdown at 8:23:21 AM on 8/18/2022 was unexpected
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:53,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,16/08/2022 09:51:52,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:59,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:59,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:59,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:59,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:59,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:59,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 17:04:58,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,15/08/2022 08:20:06,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,12/08/2022 08:05:09,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,11/08/2022 08:42:39,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,11/08/2022 08:42:33,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,11/08/2022 08:42:32,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,11/08/2022 08:42:19,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,11/08/2022 08:42:18,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,11/08/2022 08:17:50,Microsoft-Windows-WLAN-AutoConfig,10000,None,"WLAN Extensibility Module has failed to start

Module Path: C:\Windows\system32\Rtlihvs.dll

Error Code: 126

_x000D_
Error,11/
08/2022
08:13:37,
Microsoft
-
Windows-
WLAN-
AutoConfi
g,10000,N
one,WLA
N
Extensibili
ty Module
has failed
to start.

Module Path: C:\Windows\system32\Rtlihvs.dll

Error Code: 126
register
with
DCOM
within the
required
timeout._
x000D_
Error,10/
08/2022
22:38:54,
NetBT,43
21,None,
The name
""WORKG
ROUP :
1d""
could not
be
registered
on the
interface
with IP
address
192.168.6
.65. The
computer
with the
IP address
192.168.6
.131 did
not allow
the name
to be
claimed
by this
computer
."
Error,10/08/2022 16:11:30,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,10/08/2022 08:05:40,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,09/08/2022 20:13:57,bowser,8003,None,"The description for Event ID 8003 from source bowser cannot be found. Eithe

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\LanmanDatagramReceiver
UJPCSPVPRODDNB0
NetBT_Tcpip_{64EDB863-28C3-4561-AF83-DA2121FB635D}

The message resource is present but the message was not found in the message table
Microsoft
-
Windows-
Distribute
dCOM,10
010,None
,The
server
{AB8902B
4-09CA-
4BB6-
B78D-
A8F59079
A8D5} did
not
register
with
DCOM
within the
required
timeout._
x000D_
Error,05/
08/2022
11:52:22,
Microsoft
-
Windows-
WLAN-
AutoConfi
g,10000,N
one,WLA
N
Extensibili
ty Module
has failed
to start.

Module Path: C:\Windows\system32\Rtlihvs.dll

Error Code: 126
_x000D_
Error,05/
08/2022
11:24:02,
Schannel,
36871,No
ne,A fatal
error
occurred
while
creating a
TLS client
credential
. The
internal
error
state is
10013._x
000D_
Error,05/
08/2022
11:21:29,
Microsoft
-
Windows-
WLAN-
AutoConfi
g,10000,N
one,WLA
N
Extensibili
ty Module
has failed
to start.

Module Path: C:\Windows\system32\Rtlihvs.dll

Error Code: 126
_x000D_
Error,05/
08/2022
11:21:18,
Microsoft
-
Windows-
WLAN-
AutoConfi
g,10000,N
one,WLA
N
Extensibili
ty Module
has failed
to start.

Module Path: C:\Windows\system32\Rtlihvs.dll

Error Code: 126
connectio
n request
has failed.
The
attached
data
contains
the server
certificate
._x000D_
Error,26/
07/2022
15:14:43,
Schannel,
36884,No
ne,The
certificate
received
from the
remote
server
does not
contain
the
expected
name. It
is
therefore
not
possible
to
determin
e whether
we are
connectin
g to the
corr
ct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attached
Error,26/07/2022 15:14:43,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 15:14:17,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 15:14:17,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 15:13:58,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 15:13:42,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 10:44:02,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,26/07/2022 10:43:52,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,26/07/2022 09:51:23,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,26/07/2022 09:30:40,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,26/07/2022 08:39:32,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,26/07/2022 08:36:02,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,26/07/2022 08:36:01,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,26/07/2022 08:35:26,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:26,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:25,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:24,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:24,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:23,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:23,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:23,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:23,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:23,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:22,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:22,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,26/07/2022 08:35:21,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,25/07/2022 17:25:41,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,25/07/2022 17:16:10,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,25/07/2022 17:14:42,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,25/07/2022 17:08:12,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,25/07/2022 16:46:59,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,25/07/2022 16:29:36,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,25/07/2022 16:29:00,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Critical,25/07/2022 16:28:09,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,25/07/2022 16:28:16,EventLog,6008,None,The previous system shutdown at 4:07:52 PM on 7/25/2022 was unexpected
Error,25/07/2022 15:56:21,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {659CDEA7-489E-11D
Error,25/07/2022 15:52:10,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {659CDEA7-489E-11D
Error,25/07/2022 15:47:20,Schannel,36882,None,"The certificate received from the remote server was issued by an untrusted
Error,25/07/2022 14:17:23,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 14:13:22,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 14:09:21,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 14:05:20,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 14:01:19,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 13:57:18,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 13:53:17,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 13:49:16,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 13:45:14,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 13:41:13,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 11:42:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:40:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:38:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:36:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:34:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:32:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:30:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:28:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:26:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:24:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:22:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:20:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:18:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:16:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:14:24,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:12:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:10:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:08:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:06:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:04:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:02:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 11:01:40,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 11:00:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:58:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:56:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:54:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:52:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:50:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:48:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:46:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:44:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:42:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:40:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:38:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:36:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:34:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:32:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:30:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:28:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:26:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:24:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:22:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:20:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:18:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:16:23,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:14:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:12:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:10:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:08:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:06:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:04:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:04:09,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 10:02:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:00:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 10:00:07,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 09:58:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:56:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:56:06,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 09:54:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:52:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:52:04,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 09:50:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:48:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:48:01,Microsoft-Windows-DistributedCOM,10029,None,The activation of the CLSID {4991D34B-80A1-42
Error,25/07/2022 09:46:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:44:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:42:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:40:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:38:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:36:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:34:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:32:22,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:30:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:28:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:26:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:24:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:22:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:20:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:18:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:16:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:14:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:12:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:10:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:08:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:06:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:04:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:02:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 09:00:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:58:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:56:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:54:21,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:52:20,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:50:20,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:48:20,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:46:20,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:44:20,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:42:20,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:42:05,Service Control Manager,7031,None,The Connected User Experiences and Telemetry service termi
Error,25/07/2022 08:40:20,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:38:20,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:36:20,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:12:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:10:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:08:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:06:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:04:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:02:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 08:00:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 07:58:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 07:56:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 07:54:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 07:52:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 07:50:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 07:48:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 07:46:15,Microsoft-Windows-DistributedCOM,10010,None,The server {E60687F7-01A1-40AA-86AC-DB1CBF
Error,25/07/2022 07:45:07,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,25/07/2022 07:43:56,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,22/07/2022 22:45:50,Service Control Manager,7001,None,"The AppXSvc service depends on the StateRepository service
The operation completed successfully."
Error,22/07/2022 22:45:49,Service Control Manager,7023,None,"The SysMain service terminated with the following error:
The authentication service is unknown."
Error,22/07/2022 22:45:49,Service Control Manager,7023,None,"The SEMgrSvc service terminated with the following error:
The class is configured to run as a security id different from the caller"
Error,22/07/2022 22:45:49,Service Control Manager,7000,None,"The Audiosrv service failed to start due to the following erro
The service did not start due to a logon failure."
Error,22/07/2022 22:45:49,Service Control Manager,7038,None,"The Audiosrv service was unable to log on as NT AUTHORITY
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,22/07/2022 22:45:49,EventLog,6008,None,The previous system shutdown at 10:05:23 PM on 7/22/2022 was unexpecte
Critical,22/07/2022 14:46:58,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,22/07/2022 14:47:05,EventLog,6008,None,The previous system shutdown at 11:41:05 AM on 7/22/2022 was unexpecte
Critical,22/07/2022 11:15:58,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,22/07/2022 11:16:05,EventLog,6008,None,The previous system shutdown at 10:48:35 AM on 7/22/2022 was unexpecte
Error,22/07/2022 09:58:43,disk,11,None,The driver detected a controller error on \Device\Harddisk2\DR2.
Error,22/07/2022 08:33:48,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,21/07/2022 23:09:47,EventLog,6008,None,The previous system shutdown at 10:33:11 PM on 7/21/2022 was unexpecte
Error,21/07/2022 14:40:12,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Error,21/07/2022 14:40:12,Schannel,36884,None,The certificate received from the remote server does not contain the expect
Critical,21/07/2022 14:34:48,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,21/07/2022 14:34:53,EventLog,6008,None,The previous system shutdown at 1:58:49 PM on 7/21/2022 was unexpected
Error,21/07/2022 11:23:49,EventLog,6008,None,The previous system shutdown at 10:26:58 AM on 7/21/2022 was unexpecte
Error,21/07/2022 00:19:03,Microsoft-Windows-DistributedCOM,10010,None,The server {2593F8B9-4EAF-457C-B68A-50F6B8E
Error,20/07/2022 15:30:19,EventLog,6008,None,The previous system shutdown at 3:02:36 PM on 7/20/2022 was unexpected
Error,20/07/2022 13:51:26,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,19/07/2022 19:12:17,EventLog,6008,None,The previous system shutdown at 3:36:47 PM on 7/19/2022 was unexpected
Error,19/07/2022 19:12:05,Microsoft-Windows-Kernel-Boot,29,None,Windows failed fast startup with error status 0xC00000D
Error,19/07/2022 15:34:52,Service Control Manager,7000,None,"The ClickToRunSvc service failed to start due to the following
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:50,Service Control Manager,7001,None,"The AppXSvc service depends on the StateRepository service
The operation completed successfully."
Error,19/07/2022 15:34:50,Service Control Manager,7000,None,"The ASUSLinkRemote service failed to start due to the follow
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The WMIRegistrationService service failed to start due to the
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The WerSvc service was unable to log on as NT AUTHORITY\S
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The ASUSSystemAnalysis service failed to start due to the fol
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The AsusAppService service failed to start due to the followin
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The RtkAudioUniversalService service failed to start due to th
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The ASUSLinkNear service failed to start due to the following
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The cplspcon service failed to start due to the following erro
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The esifsvc service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The ICEsoundService service failed to start due to the follow
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The ASUSSwitch service failed to start due to the following e
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The ASUSSystemDiagnosis service failed to start due to the f
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The ASUSOptimization service failed to start due to the follo
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The LanmanServer service failed to start due to the following
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The LanmanServer service was unable to log on as NT AUTHO
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7001,None,"The RasMan service depends on the SstpSvc service which fa
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The TapiSrv service failed to start due to the following error:
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The WpnService service failed to start due to the following e
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The TrkWks service failed to start due to the following error:
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The TapiSrv service was unable to log on as NT AUTHORITY\N
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The WinDefend service failed to start due to the following er
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The stisvc service failed to start due to the following error:
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The SstpSvc service failed to start due to the following error:
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7001,None,"The jhi_service service depends on the iphlpsvc service whic
The dependency service or group failed to start."
Error,19/07/2022 15:34:49,Service Control Manager,7001,None,"The iphlpsvc service depends on the WinHttpAutoProxySvc s
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7001,None,"The iphlpsvc service depends on the WinHttpAutoProxySvc s
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The WinHttpAutoProxySvc service failed to start due to the f
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7001,None,"The IKEEXT service depends on the BFE service which failed t
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The BFE service failed to start due to the following error:
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The WpnService service was unable to log on as NT AUTHOR
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The DPS service failed to start due to the following error:
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The DiagTrack service failed to start due to the following erro
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The CryptSvc service failed to start due to the following erro
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The WinDefend service was unable to log on as NT AUTHORI
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The TrkWks service was unable to log on as NT AUTHORITY\S
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The stisvc service was unable to log on as NT Authority\Loca
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The SstpSvc service was unable to log on as NT Authority\Loc
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The WinHttpAutoProxySvc service was unable to log on as N
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The BFE service was unable to log on as NT AUTHORITY\Loca
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The DPS service was unable to log on as NT AUTHORITY\Loca
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The DiagTrack service was unable to log on as NT AUTHORIT
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The CryptSvc service was unable to log on as NT Authority\N
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The LanmanWorkstation service failed to start due to the fol
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The LanmanWorkstation service was unable to log on as NT
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7001,None,"The mpssvc service depends on the BFE service which failed
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The BFE service failed to start due to the following error:
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The BFE service was unable to log on as NT AUTHORITY\Loca
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The Spooler service failed to start due to the following error:
The service did not start due to a logon failure."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The Spooler service was unable to log on as NT AUTHORITY\
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7000,None,"The FA_Scheduler service failed to start due to the following
The service did not respond to the start or control request in a timely fashion."
Error,19/07/2022 15:34:49,Service Control Manager,7023,None,"The Wcmsvc service terminated with the following error:
Not enough memory resources are available to process this command."
Error,19/07/2022 15:34:49,Service Control Manager,7038,None,"The ShellHWDetection service was unable to log on as NT AU
The request is not supported.

To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)."
Error,19/07/2022 15:34:49,Service Control Manager,7001,None,"The WlanSvc service depends on the Wcmsvc service which
The operation completed successfully."
Error,19/07/2022 15:34:49,EventLog,6008,None,The previous system shutdown at 10:21:21 PM on 7/18/2022 was unexpecte
Error,15/07/2022 19:23:48,Microsoft-Windows-DistributedCOM,10005,None,"DCOM got error ""1115"" attempting to start th
{8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}"
Error,15/07/2022 19:22:41,Microsoft-Windows-DistributedCOM,10005,None,"DCOM got error ""1115"" attempting to start th
{8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}"
Error,15/07/2022 18:38:38,Microsoft-Windows-DistributedCOM,10005,None,"DCOM got error ""1115"" attempting to start th
{8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}"
Error,15/07/2022 18:36:45,Microsoft-Windows-DistributedCOM,10005,None,"DCOM got error ""1115"" attempting to start th
{8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}"
Error,15/07/2022 18:33:55,Microsoft-Windows-DistributedCOM,10005,None,"DCOM got error ""1115"" attempting to start th
{8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}"
Error,15/07/2022 18:33:54,Microsoft-Windows-DistributedCOM,10010,None,The server {5F7F3F7B-1177-4D4B-B1DB-BC6F67
Error,15/07/2022 18:33:54,Microsoft-Windows-DistributedCOM,10010,None,The server {5F7F3F7B-1177-4D4B-B1DB-BC6F67
Error,15/07/2022 18:33:54,Microsoft-Windows-DistributedCOM,10010,None,The server {5F7F3F7B-1177-4D4B-B1DB-BC6F67
Error,15/07/2022 18:33:54,Microsoft-Windows-DistributedCOM,10010,None,The server {AB93B6F1-BE76-4185-A488-A9001B
Error,15/07/2022 18:32:40,Microsoft-Windows-DistributedCOM,10005,None,"DCOM got error ""1115"" attempting to start th
{5B99FA76-721C-423C-ADAC-56D03C8A8007}"
Error,15/07/2022 18:32:38,Microsoft-Windows-DistributedCOM,10005,None,"DCOM got error ""1115"" attempting to start th
{8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}"
Error,15/07/2022 18:32:36,Microsoft-Windows-DistributedCOM,10010,None,The server {338B40F9-9D68-4B53-A793-6B9AA0
Error,15/07/2022 18:31:21,Microsoft-Windows-DistributedCOM,10005,None,"DCOM got error ""1115"" attempting to start th
{8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0}"
Error,15/07/2022 18:31:17,Microsoft-Windows-DistributedCOM,10010,None,The server windows.immersivecontrolpanel_10.
Error,15/07/2022 18:31:16,Microsoft-Windows-DistributedCOM,10010,None,The server {F9717507-6651-4EDB-BFF7-AE61517
Error,15/07/2022 18:31:15,Microsoft-Windows-DistributedCOM,10010,None,The server {F9717507-6651-4EDB-BFF7-AE61517
Error,15/07/2022 18:31:15,Microsoft-Windows-DistributedCOM,10010,None,The server {F9717507-6651-4EDB-BFF7-AE61517
Error,15/07/2022 18:31:15,Microsoft-Windows-DistributedCOM,10010,None,The server microsoft.windowscommunicationsa
Error,15/07/2022 18:31:15,Microsoft-Windows-DistributedCOM,10010,None,The server Microsoft.WindowsStore_22205.140
Error,15/07/2022 18:31:15,Microsoft-Windows-DistributedCOM,10010,None,The server Microsoft.Windows.ContentDeliveryM
Error,15/07/2022 18:31:15,Microsoft-Windows-DistributedCOM,10010,None,The server Microsoft.Windows.Search_1.14.5.19
Error,15/07/2022 07:11:33,Service Control Manager,7023,None,"The Function Discovery Resource Publication service termina
The requested address is not valid in its context."
Error,15/07/2022 07:11:33,Service Control Manager,7023,None,"The Function Discovery Resource Publication service termina
The requested address is not valid in its context."
Error,13/07/2022 22:25:28,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,13/07/2022 20:29:49,Service Control Manager,7023,None,"The Function Discovery Resource Publication service termina
The requested address is not valid in its context."
Error,13/07/2022 10:17:26,Microsoft-Windows-DistributedCOM,10010,None,The server windows.immersivecontrolpanel_10.
Error,12/07/2022 13:30:06,Microsoft-Windows-DistributedCOM,10010,None,The server B9ECED6F.ASUSPCAssistant_3.1.5.0_
Error,12/07/2022 11:58:46,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,12/07/2022 10:59:40,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Error,08/07/2022 11:11:50,bowser,8003,None,"The description for Event ID 8003 from source bowser cannot be found. Eithe

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\LanmanDatagramReceiver
KNO-PC
NetBT_Tcpip_{64EDB863-28C3-4561-AF83-DA2121FB635D}

The message resource is present but the message was not found in the message table
be
changed
by
1781352
seconds.
The time
service
will not
change
the
system
time by
more
than
54000
seconds.
Verify
that your
time and
time zone
are
correct,
and that
the time
source
time.wind
ows.com,
0x9
(ntp.m|
0x9|
0.0.0.0:12
3-
>52.148.1
14.188:12
3) is
working
properly."
Error,10/06/2022 18:32:38,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Error,10/06/2022 18:32:36,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Error,10/06/2022 18:32:35,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Error,10/06/2022 18:32:34,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Error,10/06/2022 18:32:17,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Error,10/06/2022 18:32:15,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Error,10/06/2022 18:32:14,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Error,10/06/2022 18:32:12,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Error,10/06/2022 18:32:11,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Critical,10/06/2022 16:33:31,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,10/06/2022 16:33:37,EventLog,6008,None,The previous system shutdown at 2:10:11 AM on 6/10/2022 was unexpected
Critical,09/06/2022 16:29:08,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,09/06/2022 16:29:14,EventLog,6008,None,The previous system shutdown at 1:35:13 AM on 6/9/2022 was unexpected.
Critical,09/06/2022 15:35:08,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,09/06/2022 15:35:13,EventLog,6008,None,The previous system shutdown at 10:19:27 PM on 6/8/2022 was unexpected
Critical,09/06/2022 12:19:21,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,09/06/2022 12:19:27,EventLog,6008,None,The previous system shutdown at 7:03:38 PM on 6/8/2022 was unexpected.
Critical,09/06/2022 09:03:33,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,09/06/2022 09:03:38,EventLog,6008,None,The previous system shutdown at 2:47:26 AM on 6/8/2022 was unexpected.
Critical,08/06/2022 16:47:21,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,08/06/2022 16:47:26,EventLog,6008,None,The previous system shutdown at 1:56:06 AM on 6/8/2022 was unexpected.
Critical,08/06/2022 15:56:00,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,08/06/2022 15:56:06,EventLog,6008,None,The previous system shutdown at 1:34:26 AM on 6/8/2022 was unexpected.
Error,08/06/2022 08:51:54,Schannel,36871,None,A fatal error occurred while creating a TLS client credential. The internal erro
Critical,09/05/2022 19:23:17,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,09/05/2022 19:23:17,volmgr,161,None,Dump file creation failed due to error during dump creation.
Error,09/05/2022 19:23:22,EventLog,6008,None,The previous system shutdown at 2:29:53 AM on 5/9/2022 was unexpected.
Critical,09/05/2022 15:09:47,Microsoft-Windows-Kernel-Power,41,(63),"The system has rebooted without cleanly shutting do
Error,09/05/2022 15:09:53,EventLog,6008,None,The previous system shutdown at 12:48:58 AM on 5/9/2022 was unexpected
Error,09/05/2022 15:09:45,Microsoft-Windows-Kernel-Boot,29,None,Windows failed fast startup with error status 0xC00000D
Error,09/05/2022 14:30:59,Tcpip,4199,None,The system detected an address conflict for IP address 10.7.60.121 with the syste
Error,05/05/2022 14:42:55,Service Control Manager,7023,None,"The Function Discovery Resource Publication service termina
The requested address is not valid in its context."
Error,29/04/2022 15:15:24,Microsoft-Windows-DistributedCOM,10010,None,The server {5F7F3F7B-1177-4D4B-B1DB-BC6F67
Error,29/04/2022 14:30:10,Microsoft-Windows-DistributedCOM,10010,None,The server {995C996E-D918-4A8C-A302-45719A
Error,29/04/2022 14:30:10,Microsoft-Windows-DistributedCOM,10010,None,The server {995C996E-D918-4A8C-A302-45719A
Error,29/04/2022 14:30:10,Microsoft-Windows-DistributedCOM,10010,None,The server {995C996E-D918-4A8C-A302-45719A
Error,29/04/2022 14:25:18,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,29/04/2022 14:22:58,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,29/04/2022 14:17:28,Microsoft-Windows-WindowsUpdateClient,20,Windows Update Agent,Installation Failure: Window
Error,29/04/2022 14:17:06,Microsoft-Windows-Ntfs,98,None,"Volume D: (\Device\HarddiskVolume7) needs to be taken offlin
Error,24/04/2022 08:10:41,Microsoft-Windows-Time-Service,34,None,"The time service has detected that the system time ne
Error,24/04/2022 08:10:20,Microsoft-Windows-NDIS,10317,PnP,"Miniport Corechip SR9900 USB2.0 to Fast Ethernet Adapter,
Error,24/04/2022 07:57:38,Service Control Manager,7030,None,"The Printer Extensions and Notifications service is marked as
Error,24/04/2022 07:53:54,Service Control Manager,7023,None,"The netprofm service terminated with the following error:
The device is not ready."
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 10/19/2022 was unexpected.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

on 10/19/2022 was unexpected.

ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

on 10/19/2022 was unexpected.

ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

on 10/19/2022 was unexpected.

er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
nt,Installation Failure: Windows failed to install the following update with error 0x80240017: Security Intelligence Update for Microsoft De
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
oft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetT
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 10/17/2022 was unexpected.
ervice encountered an error (5) while enabling publisher {a70ff94f-570b-4979-ba5c-e59c9feab61b} to channel Microsoft-Windows-WinIN
ed to start due to the following error:

e failed to start due to the following error:

to start due to the following error:

on the StateRepository service which failed to start because of the following error:

failed to start due to the following error:

ailed to start due to the following error:

ailed to start due to the following error:

e to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

ervice failed to start due to the following error:

tart due to the following error:

ce failed to start due to the following error:

led to start due to the following error:

ce failed to start due to the following error:

d to start due to the following error:

 service failed to start due to the following error:

to start due to the following error:

vice failed to start due to the following error:

iled to start due to the following error:

start due to the following error:

rt due to the following error:

d to start due to the following error:

failed to start due to the following error:

rvice failed to start due to the following error:

ed to start due to the following error:

unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

n the SstpSvc service which failed to start because of the following error:

art due to the following error:

e to log on as NT AUTHORITY\NetworkService with the currently configured password due to the following error:

ment Console (MMC)."

to start due to the following error:

art due to the following error:

nable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

o start due to the following error:

art due to the following error:

t due to the following error:

e to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

able to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

ble to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

e to log on as NT Authority\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

o log on as NT Authority\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

s on the iphlpsvc service which failed to start because of the following error:

on the Winmgmt service which failed to start because of the following error:

due to the following error:

ble to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

start due to the following error:

log on as NT AUTHORITY\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

tart due to the following error:

le to log on as NT Authority\NetworkService with the currently configured password due to the following error:

ment Console (MMC)."

ble to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

ce failed to start due to the following error:
ce was unable to log on as NT AUTHORITY\NetworkService with the currently configured password due to the following error:

ment Console (MMC)."

n the BFE service which failed to start because of the following error:

due to the following error:

log on as NT AUTHORITY\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

art due to the following error:

e to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

art due to the following error:

e to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

d to start due to the following error:

was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

on 10/17/2022 was unexpected.

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

on 10/15/2022 was unexpected.

on 10/15/2022 was unexpected.

nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.

on 10/14/2022 was unexpected.

ce terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service.

on 10/14/2022 was unexpected.

on 10/14/2022 was unexpected.

on 10/14/2022 was unexpected.

on 10/14/2022 was unexpected.

on 10/13/2022 was unexpected.

on 10/13/2022 was unexpected.

on 10/13/2022 was unexpected.

on 10/13/2022 was unexpected.

on 10/13/2022 was unexpected.

on 10/13/2022 was unexpected.

on 10/13/2022 was unexpected.

on 10/13/2022 was unexpected.

nt credential. The internal error state is 10013.
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
96E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
96E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.

8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
CB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
CB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
CB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
CB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
CB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
CB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
6F1-BE76-4185-A488-A9001B105B94} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
0C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 10/3/2022 was unexpected.
CB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
CB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
p with error status 0xC00000D4.
on 10/3/2022 was unexpected.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
2B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NCBCSZSJRSB-SpotifyAB.SpotifyMusic.
nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.

on 9/30/2022 was unexpected.

nt credential. The internal error state is 10013.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
oft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetT
972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NCBCSZSJRSB-SpotifyAB.SpotifyMusic.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
ause the shadow copy storage could not grow due to a user imposed limit.
nt credential. The internal error state is 10013.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
nt credential. The internal error state is 10013.
39B-6524-481C-A78C-E680D7BF086C} did not register with DCOM within the required timeout.
disk2\DR20.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
D6F.ASUSPCAssistant_3.1.5.0_x64__qmba6cd70vzyy!App.AppX7kzebfqmdxej6ev77x78grbnx1efgwnw.mca did not register with DCOM wit
nt credential. The internal error state is 10013.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
oft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetT
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

on 9/6/2022 was unexpected.

er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
oft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetT
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
oft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetT
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
nt,Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
nt credential. The internal error state is 10013.
03A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
nt credential. The internal error state is 10013.
972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
on 8/18/2022 was unexpected.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
ility Module has failed to start.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
nt credential. The internal error state is 10013.
owser cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted
equest has failed. The attached data contains the server certificate.
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 7/25/2022 was unexpected.
he CLSID {659CDEA7-489E-11D9-A9CD-000D56965251} timed out waiting for the service BITS to stop.
he CLSID {659CDEA7-489E-11D9-A9CD-000D56965251} timed out waiting for the service BITS to stop.
ver was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
he CLSID {4991D34B-80A1-4291-83B6-3328366B9097} timed out waiting for the service BITS to stop.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
s and Telemetry service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 millise
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
7F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
on the StateRepository service which failed to start because of the following error:

d with the following error:

ed with the following error:

start due to the following error:

le to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

on 7/22/2022 was unexpected.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 7/22/2022 was unexpected.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 7/22/2022 was unexpected.

nt credential. The internal error state is 10013.

on 7/21/2022 was unexpected.
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
er does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The ser
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 7/21/2022 was unexpected.
on 7/21/2022 was unexpected.
8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
on 7/20/2022 was unexpected.
nt credential. The internal error state is 10013.
on 7/19/2022 was unexpected.
p with error status 0xC00000D4.
ed to start due to the following error:

on the StateRepository service which failed to start because of the following error:

ailed to start due to the following error:

ervice failed to start due to the following error:

e to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

ce failed to start due to the following error:

led to start due to the following error:

service failed to start due to the following error:

d to start due to the following error:

start due to the following error:

rt due to the following error:

iled to start due to the following error:

to start due to the following error:

vice failed to start due to the following error:

failed to start due to the following error:

ed to start due to the following error:

unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

n the SstpSvc service which failed to start because of the following error:

art due to the following error:

to start due to the following error:

art due to the following error:

e to log on as NT AUTHORITY\NetworkService with the currently configured password due to the following error:

ment Console (MMC)."

o start due to the following error:

t due to the following error:

art due to the following error:

s on the iphlpsvc service which failed to start because of the following error:

on the WinHttpAutoProxySvc service which failed to start because of the following error:
on the WinHttpAutoProxySvc service which failed to start because of the following error:

vice failed to start due to the following error:

n the BFE service which failed to start because of the following error:

due to the following error:

nable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

due to the following error:

start due to the following error:

tart due to the following error:

able to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

e to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

o log on as NT Authority\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

e to log on as NT Authority\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

vice was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

log on as NT AUTHORITY\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

log on as NT AUTHORITY\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

ble to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

le to log on as NT Authority\NetworkService with the currently configured password due to the following error:

ment Console (MMC)."

ce failed to start due to the following error:

ce was unable to log on as NT AUTHORITY\NetworkService with the currently configured password due to the following error:

ment Console (MMC)."

n the BFE service which failed to start because of the following error:

due to the following error:

log on as NT AUTHORITY\LocalService with the currently configured password due to the following error:

ment Console (MMC)."

art due to the following error:

e to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

d to start due to the following error:

d with the following error:

was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error:

ment Console (MMC)."

on the Wcmsvc service which failed to start because of the following error:

on 7/18/2022 was unexpected.

"1115"" attempting to start the service SecurityHealthService with arguments ""Unavailable"" in order to run the server:

"1115"" attempting to start the service SecurityHealthService with arguments ""Unavailable"" in order to run the server:

"1115"" attempting to start the service SecurityHealthService with arguments ""Unavailable"" in order to run the server:

"1115"" attempting to start the service SecurityHealthService with arguments ""Unavailable"" in order to run the server:
 "1115"" attempting to start the service SecurityHealthService with arguments ""Unavailable"" in order to run the server:

F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout.
F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout.
F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout.
6F1-BE76-4185-A488-A9001B105B94} did not register with DCOM within the required timeout.
"1115"" attempting to start the service dosvc with arguments ""Unavailable"" in order to run the server:

"1115"" attempting to start the service SecurityHealthService with arguments ""Unavailable"" in order to run the server:

0F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
"1115"" attempting to start the service SecurityHealthService with arguments ""Unavailable"" in order to run the server:

ws.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with

507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.
507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.
507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout.
oft.windowscommunicationsapps_16005.14326.20970.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49
oft.WindowsStore_22205.1401.13.0_x64__8wekyb3d8bbwe!App.AppX4kq775cvjnf3kamcw69d81vz8nk5q6hq.mca did not register with D
oft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXx4zfy1ffv3wctgdz2vypnybzjkh27jhw
oft.Windows.Search_1.14.5.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not r
ce Publication service terminated with the following error:

ce Publication service terminated with the following error:

nt credential. The internal error state is 10013.

ce Publication service terminated with the following error:

ws.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with

D6F.ASUSPCAssistant_3.1.5.0_x64__qmba6cd70vzyy!App.AppX7kzebfqmdxej6ev77x78grbnx1efgwnw.mca did not register with DCOM wit
nt credential. The internal error state is 10013.
nt credential. The internal error state is 10013.
owser cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted
 ected that the system time needs to be changed by 1781352 seconds. The time service will not change the system time by more than 540
ected that the system time needs to be changed by 1781352 seconds. The time service will not change the system time by more than 540
ected that the system time needs to be changed by 1781352 seconds. The time service will not change the system time by more than 540
ected that the system time needs to be changed by 1781352 seconds. The time service will not change the system time by more than 540
ected that the system time needs to be changed by 1781352 seconds. The time service will not change the system time by more than 540
ected that the system time needs to be changed by 1781352 seconds. The time service will not change the system time by more than 540
ected that the system time needs to be changed by 1781352 seconds. The time service will not change the system time by more than 540
ected that the system time needs to be changed by 1781352 seconds. The time service will not change the system time by more than 540
ected that the system time needs to be changed by 1781352 seconds. The time service will not change the system time by more than 540
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 6/10/2022 was unexpected.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 6/9/2022 was unexpected.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 6/8/2022 was unexpected.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 6/8/2022 was unexpected.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 6/8/2022 was unexpected.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 6/8/2022 was unexpected.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 6/8/2022 was unexpected.
nt credential. The internal error state is 10013.
ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

on 5/9/2022 was unexpected.

ed without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
on 5/9/2022 was unexpected.
p with error status 0xC00000D4.
ress 10.7.60.121 with the system having network hardware address C8-5A-CF-F7-29-93. Network operations on this system may be disrup
ce Publication service terminated with the following error:

F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout.
96E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
96E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
96E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
nt,Installation Failure: Windows failed to install the following update with error 0x80240016: Intel Corporation - Display - 26.20.100.7372.
nt,Installation Failure: Windows failed to install the following update with error 0x80240009: NVIDIA - Display - 27.21.14.6231.
nt,Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel - System - 12/12/2018 12:00:00 AM - 8.
ume7) needs to be taken offline to perform a Full Chkdsk. Please run ""CHKDSK /F"" locally via the command line, or run ""REPAIR-VOLUM
ected that the system time needs to be changed by 453879 seconds. The time service will not change the system time by more than 5400
B2.0 to Fast Ethernet Adapter, {adf3a1ce-c005-4f7b-8a21-0f9f048a32aa}, had event Network Interface deleted while PNP Device still exist
tifications service is marked as an interactive service. However, the system is configured to not allow interactive services. This service ma
ed with the following error:
, or lost power unexpectedly."

, or lost power unexpectedly."

, or lost power unexpectedly."

, or lost power unexpectedly."

to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
gence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.377.405.0).
on.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.

, or lost power unexpectedly."

nel Microsoft-Windows-WinINet/Operational. This does not affect channel operation, but does affect the ability of the publisher to raise ev
e following error:

, or lost power unexpectedly."

 , or lost power unexpectedly."

WV-Microsoft.YourPhone.

liseconds: Restart the service.

to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache

to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
 to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache

WV-Microsoft.YourPhone.
WV-Microsoft.YourPhone.
, or lost power unexpectedly."

, or lost power unexpectedly."

B-SpotifyAB.SpotifyMusic.
WV-Microsoft.YourPhone.

on.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.

B-SpotifyAB.SpotifyMusic.

WV-Microsoft.YourPhone.
id not register with DCOM within the required timeout.

on.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
, or lost power unexpectedly."

to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
 on.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
WV-Microsoft.YourPhone.
on.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
WV-Microsoft.YourPhone.
WV-Microsoft.YourPhone.
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
or the installation is corrupted. You can install or repair the component on the local computer.
 to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
 to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is ip-info.ff.avast.com. The TLS connection request has failed. The attached dat
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
, or lost power unexpectedly."

cate can be validated. The TLS connection request has failed. The attached data contains the server certificate."
n will be taken in 30000 milliseconds: Restart the service.
to the correct server. The server name we were expecting is driver-updater.ff.avast.com. The TLS connection request has failed. The attac
to the correct server. The server name we were expecting is openid.avg.com. The TLS connection request has failed. The attached data co

, or lost power unexpectedly."

, or lost power unexpectedly."

to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attache
, or lost power unexpectedly."
following error:
e following error:

n the server:

n the server:

n the server:

n the server:
n the server:

n the server:

n the server:

trolpanel did not register with DCOM within the required timeout.

endar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.
hq.mca did not register with DCOM within the required timeout.
ffv3wctgdz2vypnybzjkh27jhw.mca did not register with DCOM within the required timeout.
6t6g31ep03r71y.mca did not register with DCOM within the required timeout.

trolpanel did not register with DCOM within the required timeout.
id not register with DCOM within the required timeout.

or the installation is corrupted. You can install or repair the component on the local computer.
system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x
system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x
system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x
system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x
system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x
system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x
system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x
system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x
system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x
, or lost power unexpectedly."

, or lost power unexpectedly."

, or lost power unexpectedly."

, or lost power unexpectedly."

, or lost power unexpectedly."

, or lost power unexpectedly."

, or lost power unexpectedly."

, or lost power unexpectedly."

, or lost power unexpectedly."

on this system may be disrupted as a result.

on - Display - 26.20.100.7372.
ay - 27.21.14.6231.
- 12/12/2018 12:00:00 AM - 8.5.10103.7263.
d line, or run ""REPAIR-VOLUME <drive:>"" locally or remotely via PowerShell."
ystem time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9
ed while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of
tive services. This service may not function properly."
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
e required timeout.

lity of the publisher to raise events to the channel. One common reason for this error is that the Provider is using ETW Provider Security a
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.

equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
e required timeout.
e required timeout.

equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
e required timeout.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
e required timeout.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.

n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
st has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
n request has failed. The attached data contains the server certificate.
as failed. The attached data contains the server certificate.

equest has failed. The attached data contains the server certificate.
equest has failed. The attached data contains the server certificate.
e source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
e source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
e source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
e source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
e source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
e source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
e source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
e source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
e source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->52.148.114.188:123) is working properly."
an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)"
using ETW Provider Security and has not granted enable permissions to the Event Log service identity."