Vino's Event Viewer v01c run on Windows 7 in English
Report run at 16/04/2021 2:48:45 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 15/04/2021 10:12:15 PM
Type: Error Category: 0
Event: 1552 Source: Microsoft-Windows-User Profiles Service
User hive is loaded by another process (Registry Lock) Process name: C:\Program Files\AVAST Software\Avast\aswToolsSvc.exe, PID: 3260, ProfSvc PID: 1836.

Log: 'Application' Date/Time: 15/04/2021 10:12:15 PM
Type: Error Category: 0
Event: 1552 Source: Microsoft-Windows-User Profiles Service
User hive is loaded by another process (Registry Lock) Process name: C:\Program Files\AVAST Software\Avast\aswToolsSvc.exe, PID: 3260, ProfSvc PID: 1836.

Log: 'Application' Date/Time: 15/04/2021 10:12:15 PM
Type: Error Category: 0
Event: 1552 Source: Microsoft-Windows-User Profiles Service
User hive is loaded by another process (Registry Lock) Process name: C:\Program Files\AVAST Software\Avast\aswToolsSvc.exe, PID: 3260, ProfSvc PID: 1836.

Log: 'Application' Date/Time: 15/04/2021 10:12:15 PM
Type: Error Category: 0
Event: 1552 Source: Microsoft-Windows-User Profiles Service
User hive is loaded by another process (Registry Lock) Process name: C:\Program Files\AVAST Software\Avast\aswToolsSvc.exe, PID: 3260, ProfSvc PID: 1836.

Log: 'Application' Date/Time: 15/04/2021 10:12:15 PM
Type: Error Category: 0
Event: 1552 Source: Microsoft-Windows-User Profiles Service
User hive is loaded by another process (Registry Lock) Process name: C:\Program Files\AVAST Software\Avast\aswToolsSvc.exe, PID: 3260, ProfSvc PID: 1836.

Log: 'Application' Date/Time: 15/04/2021 10:12:15 PM
Type: Error Category: 0
Event: 1552 Source: Microsoft-Windows-User Profiles Service
User hive is loaded by another process (Registry Lock) Process name: C:\Program Files\AVAST Software\Avast\aswToolsSvc.exe, PID: 3260, ProfSvc PID: 1836.

Log: 'Application' Date/Time: 15/04/2021 10:12:15 PM
Type: Error Category: 0
Event: 1552 Source: Microsoft-Windows-User Profiles Service
User hive is loaded by another process (Registry Lock) Process name: C:\Program Files\AVAST Software\Avast\aswToolsSvc.exe, PID: 3260, ProfSvc PID: 1836.

Log: 'Application' Date/Time: 15/04/2021 10:12:15 PM
Type: Error Category: 0
Event: 1552 Source: Microsoft-Windows-User Profiles Service
User hive is loaded by another process (Registry Lock) Process name: C:\Program Files\AVAST Software\Avast\aswToolsSvc.exe, PID: 3260, ProfSvc PID: 1836.

Log: 'Application' Date/Time: 14/04/2021 4:12:31 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SnippingTool.exe, version: 10.0.19041.746, time stamp: 0x08f6c8b3 Faulting module name: combase.dll, version: 10.0.19041.844, time stamp: 0x98fb6ff0 Exception code: 0xc0000005 Fault offset: 0x00074314 Faulting process ID: 0xbfc Faulting application start time: 0x01d730e44c002f99 Faulting application path: C:\Windows\System32\SnippingTool.exe Faulting module path: C:\WINDOWS\System32\combase.dll Report ID: 3ada0071-f362-4d24-8682-51d50c3f1a65 Faulting package full name:  Faulting package-relative application ID: 

Log: 'Application' Date/Time: 12/04/2021 7:36:00 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program explorer.exe version 10.0.19041.867 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.  Process ID: 4a8  Start Time: 01d72f4b864ee209  Termination Time: 25  Application Path: C:\Windows\explorer.exe  Report Id: 1513b5a5-180f-4cb0-9e3e-1a9b76ef076f  Faulting package full name:   Faulting package-relative application ID:   Hang type: Unknown 

Log: 'Application' Date/Time: 12/04/2021 3:12:37 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program explorer.exe version 10.0.19041.867 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.  Process ID: 25c0  Start Time: 01d72f47d3f76510  Termination Time: 21  Application Path: C:\Windows\explorer.exe  Report Id: e3152c84-80bd-4319-b1ba-c72d19331645  Faulting package full name:   Faulting package-relative application ID:   Hang type: Unknown 

Log: 'Application' Date/Time: 09/04/2021 12:09:12 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SnippingTool.exe, version: 10.0.19041.746, time stamp: 0x08f6c8b3 Faulting module name: combase.dll, version: 10.0.19041.844, time stamp: 0x98fb6ff0 Exception code: 0xc0000005 Fault offset: 0x00074314 Faulting process ID: 0x36b0 Faulting application start time: 0x01d72cd46ced903b Faulting application path: C:\Windows\System32\SnippingTool.exe Faulting module path: C:\WINDOWS\System32\combase.dll Report ID: 92219f2b-1287-4094-8d74-72cf33bc654d Faulting package full name:  Faulting package-relative application ID: 

Log: 'Application' Date/Time: 08/04/2021 2:34:55 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: SMMVSplitter_Business.exe, version: 6.0.1607.15, time stamp: 0x5788f14f Faulting module name: SMM_OCXSlider.ocx, version: 1.5.1607.4, time stamp: 0x5788f0f0 Exception code: 0xc0000094 Fault offset: 0x002731f9 Faulting process ID: 0xbeec Faulting application start time: 0x01d72c6b6b70ab8b Faulting application path: C:\Program Files\Solveig Multimedia\v6.0.1607.15\SMMVSplitter_Business.exe Faulting module path: C:\Program Files\Solveig Multimedia\v6.0.1607.15\SMM_OCXSlider.ocx Report ID: 19b24285-3292-40cd-a9f1-94a1dd20adae Faulting package full name:  Faulting package-relative application ID: 

Log: 'Application' Date/Time: 08/04/2021 5:19:10 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program SMMVSplitter_Business.exe version 6.0.1607.15 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.  Process ID: 1514  Start Time: 01d72c36806f9d09  Termination Time: 22  Application Path: C:\Program Files\Solveig Multimedia\v6.0.1607.15\SMMVSplitter_Business.exe  Report Id: bb4e2695-0e92-4156-b298-b3b7e5ca65c4  Faulting package full name:   Faulting package-relative application ID:   Hang type: Cross-thread 

Log: 'Application' Date/Time: 08/04/2021 12:52:44 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ffmpeg.exe, version: 0.0.0.0, time stamp: 0x67d825ff Faulting module name: avutil-55.dll, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x40000015 Fault offset: 0x0000e5b7 Faulting process ID: 0x1458 Faulting application start time: 0x01d72c1168079ee7 Faulting application path: C:\Program Files\iDealshare\VideoGo 7\ffmpeg.exe Faulting module path: C:\Program Files\iDealshare\VideoGo 7\avutil-55.dll Report ID: d4504ea2-664e-4889-b43c-9069c653e9b5 Faulting package full name:  Faulting package-relative application ID: 

Log: 'Application' Date/Time: 08/04/2021 12:52:38 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ffmpeg.exe, version: 0.0.0.0, time stamp: 0x67d825ff Faulting module name: avutil-55.dll, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x40000015 Fault offset: 0x0000e5b7 Faulting process ID: 0xe0c Faulting application start time: 0x01d72c1148bb22ae Faulting application path: C:\Program Files\iDealshare\VideoGo 7\ffmpeg.exe Faulting module path: C:\Program Files\iDealshare\VideoGo 7\avutil-55.dll Report ID: e4a764b9-d694-43b6-99a5-85ac610ec137 Faulting package full name:  Faulting package-relative application ID: 

Log: 'Application' Date/Time: 08/04/2021 12:52:07 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ffmpeg.exe, version: 0.0.0.0, time stamp: 0x67d825ff Faulting module name: avutil-55.dll, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x40000015 Fault offset: 0x0000e5b7 Faulting process ID: 0x1cf4 Faulting application start time: 0x01d72c115b3035e7 Faulting application path: C:\Program Files\iDealshare\VideoGo 7\ffmpeg.exe Faulting module path: C:\Program Files\iDealshare\VideoGo 7\avutil-55.dll Report ID: b17ffff4-9770-4035-826b-05e3c8689736 Faulting package full name:  Faulting package-relative application ID: 

Log: 'Application' Date/Time: 08/04/2021 12:51:46 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ffmpeg.exe, version: 0.0.0.0, time stamp: 0x67d825ff Faulting module name: avutil-55.dll, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x40000015 Fault offset: 0x0000e5b7 Faulting process ID: 0x318c Faulting application start time: 0x01d72c1156337956 Faulting application path: C:\Program Files\iDealshare\VideoGo 7\ffmpeg.exe Faulting module path: C:\Program Files\iDealshare\VideoGo 7\avutil-55.dll Report ID: 2cd86925-b2e8-4b3c-b567-f53860d56627 Faulting package full name:  Faulting package-relative application ID: 

Log: 'Application' Date/Time: 08/04/2021 12:51:37 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ffmpeg.exe, version: 0.0.0.0, time stamp: 0x67d825ff Faulting module name: avutil-55.dll, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x40000015 Fault offset: 0x0000e5b7 Faulting process ID: 0x36dc Faulting application start time: 0x01d72c1150ac5e81 Faulting application path: C:\Program Files\iDealshare\VideoGo 7\ffmpeg.exe Faulting module path: C:\Program Files\iDealshare\VideoGo 7\avutil-55.dll Report ID: f4e47937-68fd-4a50-b006-5becd2ec1968 Faulting package full name:  Faulting package-relative application ID: 

Log: 'Application' Date/Time: 08/04/2021 12:51:28 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ffmpeg.exe, version: 0.0.0.0, time stamp: 0x67d825ff Faulting module name: avutil-55.dll, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x40000015 Fault offset: 0x0000e5b7 Faulting process ID: 0x1c50 Faulting application start time: 0x01d72c1148052553 Faulting application path: C:\Program Files\iDealshare\VideoGo 7\ffmpeg.exe Faulting module path: C:\Program Files\iDealshare\VideoGo 7\avutil-55.dll Report ID: 81a6b419-efee-4d75-8db6-8d9be1062383 Faulting package full name:  Faulting package-relative application ID: 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 16/04/2021 1:51:49 AM
Type: Warning Category: 3
Event: 3036 Source: Microsoft-Windows-Search
Crawl could not be completed on content source <iehistory://{S-1-5-21-198903158-1304534811-4163729061-1000}/>.

Context:  Application, SystemIndex Catalog

Details:
	An internal error occurred in the Microsoft Windows HTTP Services  (HRESULT : 0x80072ee4) (0x80072ee4)


Log: 'Application' Date/Time: 15/04/2021 10:11:50 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, DMWmiBridgeProv1, has been registered in the Windows Management Instrumentation namespace root\cimv2\mdm\dmmap to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Log: 'Application' Date/Time: 15/04/2021 10:11:50 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, DMWmiBridgeProv1, has been registered in the Windows Management Instrumentation namespace root\cimv2\mdm\dmmap to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Log: 'Application' Date/Time: 15/04/2021 10:11:50 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, DMWmiBridgeProv1, has been registered in the Windows Management Instrumentation namespace root\cimv2\mdm\dmmap to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Log: 'Application' Date/Time: 15/04/2021 10:11:50 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, DMWmiBridgeProv, has been registered in the Windows Management Instrumentation namespace root\cimv2\mdm\dmmap to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Log: 'Application' Date/Time: 15/04/2021 10:11:50 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, DMWmiBridgeProv, has been registered in the Windows Management Instrumentation namespace root\cimv2\mdm\dmmap to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Log: 'Application' Date/Time: 15/04/2021 10:11:50 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, DMWmiBridgeProv, has been registered in the Windows Management Instrumentation namespace root\cimv2\mdm\dmmap to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Log: 'Application' Date/Time: 14/04/2021 10:31:05 PM
Type: Warning Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open procedure for service "aspnet_state" in DLL "C:\Windows\System32\aspnet_counters.dll" failed with error code Unspecified error. Performance data for this service will not be available.

Log: 'Application' Date/Time: 14/04/2021 10:31:05 PM
Type: Warning Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open procedure for service "ASP.NET_4.0.30319" in DLL "C:\Windows\System32\aspnet_counters.dll" failed with error code Unspecified error. Performance data for this service will not be available.

Log: 'Application' Date/Time: 14/04/2021 10:31:05 PM
Type: Warning Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open procedure for service "ASP.NET" in DLL "C:\Windows\System32\aspnet_counters.dll" failed with error code Unspecified error. Performance data for this service will not be available.

Log: 'Application' Date/Time: 14/04/2021 10:31:05 PM
Type: Warning Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open procedure for service ".NETFramework" in DLL "C:\WINDOWS\system32\mscoree.dll" failed with error code The system cannot find the file specified.. Performance data for this service will not be available.

Log: 'Application' Date/Time: 13/04/2021 6:28:31 AM
Type: Warning Category: 0
Event: 12348 Source: VSS
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{bd3b32c8-f678-4f2e-bc9c-5c824676b2f2}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Automatically choosing a diff-area volume
   Processing EndPrepareSnapshots

Context:
   Execution Context: System Provider

Log: 'Application' Date/Time: 13/04/2021 6:28:31 AM
Type: Warning Category: 0
Event: 12348 Source: VSS
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{bd3b32c8-f678-4f2e-bc9c-5c824676b2f2}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Automatically choosing a diff-area volume
   Processing EndPrepareSnapshots

Context:
   Execution Context: System Provider

Log: 'Application' Date/Time: 13/04/2021 6:28:31 AM
Type: Warning Category: 0
Event: 12348 Source: VSS
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{bd3b32c8-f678-4f2e-bc9c-5c824676b2f2}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Removing auto-release shadow copies
   Loading provider

Context:
   Execution Context: System Provider

Log: 'Application' Date/Time: 13/04/2021 6:02:18 AM
Type: Warning Category: 0
Event: 12348 Source: VSS
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{f6dff843-0000-0000-007e-000000000000}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Automatically choosing a diff-area volume
   Processing EndPrepareSnapshots

Context:
   Execution Context: System Provider

Log: 'Application' Date/Time: 13/04/2021 6:02:18 AM
Type: Warning Category: 0
Event: 12348 Source: VSS
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{f6dff843-0000-0000-007e-000000000000}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Automatically choosing a diff-area volume
   Processing EndPrepareSnapshots

Context:
   Execution Context: System Provider

Log: 'Application' Date/Time: 13/04/2021 6:02:17 AM
Type: Warning Category: 0
Event: 12348 Source: VSS
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{f6dff843-0000-0000-007e-000000000000}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Removing auto-release shadow copies
   Loading provider

Context:
   Execution Context: System Provider

Log: 'Application' Date/Time: 13/04/2021 5:48:41 AM
Type: Warning Category: 0
Event: 12348 Source: VSS
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{4c663843-0000-0000-007e-000000000000}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Automatically choosing a diff-area volume
   Processing EndPrepareSnapshots

Context:
   Execution Context: System Provider

Log: 'Application' Date/Time: 13/04/2021 5:48:41 AM
Type: Warning Category: 0
Event: 12348 Source: VSS
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{4c663843-0000-0000-007e-000000000000}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Automatically choosing a diff-area volume
   Processing EndPrepareSnapshots

Context:
   Execution Context: System Provider

Log: 'Application' Date/Time: 13/04/2021 5:48:40 AM
Type: Warning Category: 0
Event: 12348 Source: VSS
Volume Shadow Copy Service warning: VSS was denied access to the root of volume \\?\Volume{4c663843-0000-0000-007e-000000000000}\. Denying administrators from accessing volume roots can cause many unexpected failures, and will prevent VSS from functioning properly.  Check security on the volume, and try the operation again. 

Operation:
   Removing auto-release shadow copies
   Loading provider

Context:
   Execution Context: System Provider

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/04/2021 11:49:04 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 10/04/2021 5:28:59 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 10/04/2021 1:51:23 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 08/04/2021 8:05:54 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 08/04/2021 7:40:35 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 07/04/2021 5:43:24 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 16/04/2021 1:51:49 AM
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-DistributedCOM
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error: "2147942767" Happened while starting this command: C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 14/04/2021 11:40:52 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 16/04/2021 4:31:55 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 16/04/2021 4:31:53 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 16/04/2021 4:31:17 AM
Type: Warning Category: 0
Event: 16001 Source: AFD
A TDI filter (\Driver\networx) was detected. This filter has not been certified by Microsoft and may cause system instability.

Log: 'System' Date/Time: 16/04/2021 4:31:14 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_1BBB&PID_0168\6SNJAYNV5LQKS8AQ.

Log: 'System' Date/Time: 16/04/2021 12:47:49 AM
Type: Warning Category: 0
Event: 157 Source: disk
Disk 5 has been surprise removed.

Log: 'System' Date/Time: 15/04/2021 10:13:10 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 15/04/2021 10:13:08 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 15/04/2021 10:11:25 PM
Type: Warning Category: 0
Event: 16001 Source: AFD
A TDI filter (\Driver\networx) was detected. This filter has not been certified by Microsoft and may cause system instability.

Log: 'System' Date/Time: 15/04/2021 10:11:19 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_1BBB&PID_0168\6SNJAYNV5LQKS8AQ.

Log: 'System' Date/Time: 15/04/2021 8:48:56 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 15/04/2021 8:48:54 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 15/04/2021 8:48:13 AM
Type: Warning Category: 0
Event: 16001 Source: AFD
A TDI filter (\Driver\networx) was detected. This filter has not been certified by Microsoft and may cause system instability.

Log: 'System' Date/Time: 15/04/2021 8:48:10 AM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_1BBB&PID_0168\6SNJAYNV5LQKS8AQ.

Log: 'System' Date/Time: 14/04/2021 10:17:55 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 14/04/2021 10:17:52 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 14/04/2021 10:17:18 PM
Type: Warning Category: 0
Event: 16001 Source: AFD
A TDI filter (\Driver\networx) was detected. This filter has not been certified by Microsoft and may cause system instability.

Log: 'System' Date/Time: 14/04/2021 10:17:14 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device USB\VID_1BBB&PID_0168\6SNJAYNV5LQKS8AQ.

Log: 'System' Date/Time: 14/04/2021 11:43:51 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 14/04/2021 11:43:49 AM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}  and APPID  {15C20B67-12E7-4BB6-92BB-7AFF07997402}  to the user DESKTOPTOWER\Joe SID (S-1-5-21-198903158-1304534811-4163729061-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 14/04/2021 11:43:11 AM
Type: Warning Category: 0
Event: 16001 Source: AFD
A TDI filter (\Driver\networx) was detected. This filter has not been certified by Microsoft and may cause system instability.