I ran the Framework site.
Vino's Event Viewer v01c run on Windows XP in English
Report run at 10/02/2017 4:30:42 PM
Note: All dates below are in the format dd/mm/yyyy
Reply
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/02/2017 3:13:21 PM
Type: error Category: 0
Event: 4311 Source: NetBT
Initialization failed because the driver device could not be created.
Log: 'System' Date/Time: 10/02/2017 3:13:16 PM
Type: error Category: 0
Event: 3095 Source: NETLOGON
This computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration.
Log: 'System' Date/Time: 10/02/2017 3:11:42 PM
Type: error Category: 0
Event: 10005 Source: DCOM
DCOM got error "%1084" attempting to start the service EventSystem with arguments "" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF}
Log: 'System' Date/Time: 10/02/2017 3:10:37 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Tweaking Run As System 0033 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/02/2017 3:10:37 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Tweaking Run As System 0033 service to connect.
Log: 'System' Date/Time: 10/02/2017 3:10:28 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Tweaking Run As System 0032 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/02/2017 3:10:28 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Tweaking Run As System 0032 service to connect.
Log: 'System' Date/Time: 10/02/2017 3:10:17 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Tweaking Run As System 0031 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/02/2017 3:10:17 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Tweaking Run As System 0031 service to connect.
Log: 'System' Date/Time: 10/02/2017 3:10:11 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Tweaking Run As System 0030 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/02/2017 3:10:11 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Tweaking Run As System 0030 service to connect.
Log: 'System' Date/Time: 10/02/2017 3:10:07 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Tweaking Run As System 0029 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/02/2017 3:10:07 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Tweaking Run As System 0029 service to connect.
Log: 'System' Date/Time: 10/02/2017 3:10:05 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Tweaking Run As System 0028 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/02/2017 3:10:05 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Tweaking Run As System 0028 service to connect.
Log: 'System' Date/Time: 10/02/2017 3:10:02 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Tweaking Run As System 0027 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/02/2017 3:10:02 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Tweaking Run As System 0027 service to connect.
Log: 'System' Date/Time: 10/02/2017 3:10:00 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Tweaking Run As System 0026 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Log: 'System' Date/Time: 10/02/2017 3:10:00 PM
Type: error Category: 0
Event: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Tweaking Run As System 0026 service to connect.
Log: 'System' Date/Time: 10/02/2017 3:09:58 PM
Type: error Category: 0
Event: 7000 Source: Service Control Manager
The Tweaking Run As System 0025 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/02/2017 3:13:27 PM
Type: warning Category: 0
Event: 3 Source: Print
Printer HP Photosmart C7200 series fax was deleted.
Log: 'System' Date/Time: 10/02/2017 2:29:12 PM
Type: warning Category: 0
Event: 1003 Source: Dhcp
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000D56913129. The following error occurred: The operation was canceled by the user. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
Log: 'System' Date/Time: 10/02/2017 1:12:43 PM
Type: warning Category: 0
Event: 1003 Source: Dhcp
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000D56913129. The following error occurred: The operation was canceled by the user. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
Log: 'System' Date/Time: 10/02/2017 12:46:31 PM
Type: warning Category: 0
Event: 1003 Source: Dhcp
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000D56913129. The following error occurred: The operation was canceled by the user. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
Log: 'System' Date/Time: 10/02/2017 11:56:10 AM
Type: warning Category: 0
Event: 1003 Source: Dhcp
Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 000D56913129. The following error occurred: The operation was canceled by the user. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
Log: 'System' Date/Time: 16/01/2017 2:30:57 AM
Type: warning Category: 0
Event: 36 Source: W32Time
The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.
Log: 'System' Date/Time: 14/01/2017 12:53:52 PM
Type: warning Category: 0
Event: 50 Source: Fastfat
{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
Log: 'System' Date/Time: 14/01/2017 12:20:40 PM
Type: warning Category: 32
Event: 15200 Source: WPDMTPDriver
MTP USB Driver has cancelled the operation 0x1009
Log: 'System' Date/Time: 05/01/2017 3:58:11 PM
Type: warning Category: 32
Event: 15200 Source: WPDMTPDriver
MTP USB Driver has cancelled the operation 0x1008
Vino's Event Viewer v01c run on Windows XP in English
Report run at 10/02/2017 4:46:31 PM
----------------------------------------------------------------------------------------------------------------------------------------------
Note: All dates below are in the format dd/mm/yyyy
Reply#2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 10/02/2017 3:09:14 PM
Type: error Category: 8
Event: 4689 Source: COM+
The run-time environment has detected an inconsistency in its internal state. This indicates a potential instability in the process that could be caused by the custom components running in the COM+ application, the components they make use of, or other factors. Error in f:\xpsp3\com\com1x\src\comsvcs\package\cpackage.cpp(1184), hr = 8007043c: InitEventCollector failed
Log: 'Application' Date/Time: 10/02/2017 3:09:11 PM
Type: error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Log: 'Application' Date/Time: 10/02/2017 3:09:11 PM
Type: error Category: 50
Event: 4609 Source: EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
Log: 'Application' Date/Time: 10/02/2017 3:09:11 PM
Type: error Category: 0
Event: 4101 Source: VSS
Volume Shadow Copy Service error: Cannot obtain the collection 'Applications' from the COM+ catalog [0x8007043c].
Log: 'Application' Date/Time: 10/02/2017 3:08:58 PM
Type: error Category: 8
Event: 4689 Source: COM+
The run-time environment has detected an inconsistency in its internal state. This indicates a potential instability in the process that could be caused by the custom components running in the COM+ application, the components they make use of, or other factors. Error in f:\xpsp3\com\com1x\src\comsvcs\package\cpackage.cpp(1184), hr = 8007043c: InitEventCollector failed
Log: 'Application' Date/Time: 10/02/2017 3:08:55 PM
Type: error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Log: 'Application' Date/Time: 10/02/2017 3:08:55 PM
Type: error Category: 50
Event: 4609 Source: EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
Log: 'Application' Date/Time: 10/02/2017 3:08:55 PM
Type: error Category: 0
Event: 4101 Source: VSS
Volume Shadow Copy Service error: Cannot obtain the collection 'Applications' from the COM+ catalog [0x8007043c].
Log: 'Application' Date/Time: 10/02/2017 3:03:14 PM
Type: error Category: 0
Event: 4 Source: WinMgmt
Failed to load MOF C:\E63CA3A6368B7F0147E233DF61DFDC\I386\LICWMI.MOF while recovering repository file.
Log: 'Application' Date/Time: 10/02/2017 3:03:14 PM
Type: error Category: 0
Event: 4 Source: WinMgmt
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V4.0.30319\MOF\SERVICEMODEL35.MOF while recovering repository file.
Log: 'Application' Date/Time: 10/02/2017 3:03:14 PM
Type: error Category: 0
Event: 4 Source: WinMgmt
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V4.0.30319\MOF\SERVICEMODEL.MOF while recovering repository file.
Log: 'Application' Date/Time: 10/02/2017 3:03:13 PM
Type: error Category: 0
Event: 4 Source: WinMgmt
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V3.0\WINDOWS COMMUNICATION FOUNDATION\SERVICEMODEL.MOF while recovering repository file.
Log: 'Application' Date/Time: 10/02/2017 3:03:13 PM
Type: error Category: 0
Event: 4 Source: WinMgmt
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V2.0.50727\CLR.MOF while recovering repository file.
Log: 'Application' Date/Time: 10/02/2017 3:03:13 PM
Type: error Category: 0
Event: 4 Source: WinMgmt
Failed to load MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V2.0.50727\ASPNET.MOF while recovering repository file.
Log: 'Application' Date/Time: 10/02/2017 3:03:05 PM
Type: error Category: 0
Event: 4 Source: WinMgmt
Failed to load MOF C:\WINDOWS\SOFTWAREDISTRIBUTION\DOWNLOAD\16B2C96A0C41F4DFDB4D3CC228A4F819\LICWMI.MOF while recovering repository file.
Log: 'Application' Date/Time: 10/02/2017 3:02:23 PM
Type: error Category: 0
Event: 4101 Source: VSS
Volume Shadow Copy Service error: Cannot obtain the collection 'Applications' from the COM+ catalog [0x8007043c].
Log: 'Application' Date/Time: 10/02/2017 3:00:07 PM
Type: error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Log: 'Application' Date/Time: 10/02/2017 3:00:07 PM
Type: error Category: 50
Event: 4609 Source: EventSystem
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\comxp_sp3\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
Log: 'Application' Date/Time: 10/02/2017 2:59:51 PM
Type: error Category: 0
Event: 4101 Source: VSS
Volume Shadow Copy Service error: Cannot obtain the collection 'Applications' from the COM+ catalog [0x8007043c].
Log: 'Application' Date/Time: 10/02/2017 2:57:11 PM
Type: error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 10/02/2017 4:25:31 PM
Type: warning Category: 1
Event: 1020 Source: ASP.NET 4.0.30319.0
Updates to the IIS metabase were aborted because IIS is either not installed or is disabled on this machine. To configure ASP.NET to run in IIS, please install or enable IIS and re-register ASP.NET using aspnet_regiis.exe /i.
Log: 'Application' Date/Time: 10/02/2017 3:04:18 PM
Type: warning Category: 0
Event: 5603 Source: WinMgmt
A provider, OffProv, has been registered in the WMI namespace, Root\MSAPPS, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
Log: 'Application' Date/Time: 10/02/2017 3:04:18 PM
Type: warning Category: 0
Event: 5603 Source: WinMgmt
A provider, OffProv, has been registered in the WMI namespace, Root\MSAPPS, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
Log: 'Application' Date/Time: 10/02/2017 3:04:11 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, 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: 10/02/2017 3:04:11 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, 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: 10/02/2017 3:04:06 PM
Type: warning Category: 0
Event: 5603 Source: WinMgmt
A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
Log: 'Application' Date/Time: 10/02/2017 3:04:06 PM
Type: warning Category: 0
Event: 5603 Source: WinMgmt
A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
Log: 'Application' Date/Time: 10/02/2017 3:04:03 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, 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: 10/02/2017 3:04:03 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, 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: 10/02/2017 3:04:03 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, 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: 10/02/2017 3:03:47 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, 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: 10/02/2017 3:03:47 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, 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: 10/02/2017 3:03:46 PM
Type: warning Category: 0
Event: 5603 Source: WinMgmt
A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
Log: 'Application' Date/Time: 10/02/2017 3:03:46 PM
Type: warning Category: 0
Event: 5603 Source: WinMgmt
A provider, Rsop Planning Mode Provider, has been registered in the WMI namespace, root\RSOP, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
Log: 'Application' Date/Time: 10/02/2017 3:03:45 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, 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: 10/02/2017 3:03:45 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, 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: 10/02/2017 3:03:45 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, 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: 10/02/2017 3:03:27 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, 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: 10/02/2017 3:03:27 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, 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: 10/02/2017 3:03:27 PM
Type: warning Category: 0
Event: 63 Source: WinMgmt
A provider, CmdTriggerConsumer, has been registered in the WMI namespace, Root\cimv2, 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.
Edited by john god, 10 February 2017 - 03:48 PM.