Thanks for the response, the output from the program is:
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 01/01/2015 20:56:05
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 01/01/2015 20:56:00
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-08T20:56:00Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:47:54
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:47:54Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:47:24
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:47:24Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:47:23
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: mmc.exe, version: 6.3.9600.16384, time stamp: 0x5215ef8f Faulting module name: DUser.dll, version: 6.3.9600.16384, time stamp: 0x5215daf7 Exception code: 0xc0000005 Fault offset: 0x0000000000001118 Faulting process ID: 0xe08 Faulting application start time: 0x01d0253191ee05cd Faulting application path: C:\WINDOWS\system32\mmc.exe Faulting module path: C:\WINDOWS\system32\DUser.dll Report ID: 384576a4-912e-11e4-8266-74d02b29c5ad Faulting package full name: Faulting package-relative application ID:
Log: 'Application' Date/Time: 31/12/2014 20:46:54
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:46:54Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:46:24
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:46:24Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:45:54
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:45:54Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:45:24
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:45:24Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:44:54
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:44:54Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:44:24
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:44:24Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:43:54
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:43:54Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:43:24
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:43:24Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:42:54
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:42:54Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:42:24
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:42:24Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:41:54
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:41:54Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:41:24
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:41:24Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:40:54
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:40:54Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:40:24
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:40:24Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:39:54
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:39:54Z. Error Code: 0x80070002.
Log: 'Application' Date/Time: 31/12/2014 20:39:24
Type: Error Category: 0
Event: 16385 Source: Microsoft-Windows-Security-SPP
Failed to schedule Software Protection service for re-start at 2114-12-07T20:39:24Z. Error Code: 0x80070002.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 01/01/2015 01:26:49
Type: Information Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-246605679-1900367330-1637964401-1000_Classes:
Process 868 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-246605679-1900367330-1637964401-1000_CLASSES
Log: 'Application' Date/Time: 01/01/2015 01:26:49
Type: Information Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-246605679-1900367330-1637964401-1000:
Process 868 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-246605679-1900367330-1637964401-1000
Log: 'Application' Date/Time: 31/12/2014 20:54:51
Type: Information Category: 0
Event: 1000 Source: Microsoft-Windows-LoadPerf
Performance counters for the WmiApRpl (WmiApRpl) service were loaded successfully. The Record Data in the data section contains the new index values assigned to this service.
Log: 'Application' Date/Time: 31/12/2014 20:54:51
Type: Information Category: 0
Event: 1001 Source: Microsoft-Windows-LoadPerf
Performance counters for the WmiApRpl (WmiApRpl) service were removed successfully. The Record Data contains the new values of the system Last Counter and Last Help registry entries.
Log: 'Application' Date/Time: 31/12/2014 20:48:44
Type: Information Category: 0
Event: 5617 Source: Microsoft-Windows-WMI
Windows Management Instrumentation Service subsystems initialized successfully
Log: 'Application' Date/Time: 31/12/2014 20:48:43
Type: Information Category: 0
Event: 5615 Source: Microsoft-Windows-WMI
Windows Management Instrumentation Service started sucessfully
Log: 'Application' Date/Time: 31/12/2014 20:48:42
Type: Information Category: 0
Event: 1531 Source: Microsoft-Windows-User Profiles Service
The User Profile Service has started successfully.
Log: 'Application' Date/Time: 31/12/2014 20:48:15
Type: Information Category: 0
Event: 1532 Source: Microsoft-Windows-User Profiles Service
The User Profile Service has stopped.
Log: 'Application' Date/Time: 31/12/2014 20:48:15
Type: Information Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-246605679-1900367330-1637964401-1000_Classes:
Process 860 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-246605679-1900367330-1637964401-1000_CLASSES
Log: 'Application' Date/Time: 31/12/2014 20:48:15
Type: Information Category: 0
Event: 1530 Source: Microsoft-Windows-User Profiles Service
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required. DETAIL - 1 user registry handles leaked from \Registry\User\S-1-5-21-246605679-1900367330-1637964401-1000:
Process 860 (\Device\HarddiskVolume2\Windows\System32\svchost.exe) has opened key \REGISTRY\USER\S-1-5-21-246605679-1900367330-1637964401-1000
Log: 'Application' Date/Time: 31/12/2014 20:48:15
Type: Information Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.
Log: 'Application' Date/Time: 31/12/2014 20:47:29
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: mmc.exe P2: 6.3.9600.16384 P3: 5215ef8f P4: DUser.dll P5: 6.3.9600.16384 P6: 5215daf7 P7: c0000005 P8: 0000000000001118 P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_mmc.exe_9ee38e2d43b8f7521418b2a68f929763f86c42_433512da_0339c2f0 Analysis symbol: Rechecking for solution: 0 Report ID: 384576a4-912e-11e4-8266-74d02b29c5ad Report Status: 36870 Hashed bucket:
Log: 'Application' Date/Time: 31/12/2014 20:45:26
Type: Information Category: 0
Event: 4004 Source: Microsoft-Windows-Winlogon
The Windows log-on process has failed to terminate the currently logged on user's processes.
Log: 'Application' Date/Time: 31/12/2014 20:42:44
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: ScriptedDiagFailure Response: Not available Cab Id: 0 Problem signature: P1: Microsoft Corporation.WindowsUpdateDiagnostic.5.0 P2: RC_GENWUError/0x80070422 P3: 1.0.0.0 P4: Default P5: P6: P7: P8: P9: P10: Attached files: C:\Users\PC\AppData\Local\Temp\msdtadmin\_E2D21686-0D87-4861-9EFD-999FF8E468F7_\PkgD464.cab These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_Microsoft Corpor_a63ad3a7c41c3a5adc8f1460454c97242141f_00000000_cab_0e18d52f Analysis symbol: Rechecking for solution: 0 Report ID: 3f2dd925-912c-11e4-8266-74d02b29c5ad Report Status: 32770 Hashed bucket:
Log: 'Application' Date/Time: 31/12/2014 20:42:44
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: WindowsUpdateFailure2 Response: Not available Cab Id: 0 Problem signature: P1: 7.9.9600.17404 P2: 80246008 P3: 646551A5-540A-46D3-9D4D-2B06B93A2D2D P4: Download P5: 101 P6: Unmanaged {9482F4B4-E343-43B6-B170-9A65BC822C77} P7: 80080005 P8: P9: P10: Attached files: C:\Windows\WindowsUpdate.log C:\Windows\SoftwareDistribution\ReportingEvents.log These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.9.9600.17404_e23999a1f94af75439855dd45a38d3cb3f523190_00000000_cab_0ce231a7 Analysis symbol: Rechecking for solution: 0 Report ID: b02ac04e-910c-11e4-8264-74d02b29c5ad Report Status: 32770 Hashed bucket:
Log: 'Application' Date/Time: 31/12/2014 20:42:44
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: WindowsUpdateFailure2 Response: Not available Cab Id: 0 Problem signature: P1: 7.9.9600.17404 P2: 80246008 P3: 646551A5-540A-46D3-9D4D-2B06B93A2D2D P4: Download P5: 101 P6: Unmanaged {9482F4B4-E343-43B6-B170-9A65BC822C77} P7: 80080005 P8: P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.9.9600.17404_e23999a1f94af75439855dd45a38d3cb3f523190_00000000_0172d158 Analysis symbol: Rechecking for solution: 0 Report ID: abe0416e-9127-11e4-8266-74d02b29c5ad Report Status: 32770 Hashed bucket:
Log: 'Application' Date/Time: 31/12/2014 20:42:44
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: WindowsUpdateFailure2 Response: Not available Cab Id: 0 Problem signature: P1: 7.9.9600.17404 P2: 80246008 P3: E31A84F9-17C3-41BF-BD6D-F24525D8757D P4: Download P5: 101 P6: Unmanaged {9482F4B4-E343-43B6-B170-9A65BC822C77} P7: 80080005 P8: P9: P10: Attached files: C:\Windows\WindowsUpdate.log C:\Windows\SoftwareDistribution\ReportingEvents.log These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.9.9600.17404_d5e675b2a280cc91abf74f6bee0335c7b7ab78_00000000_cab_073e31c7 Analysis symbol: Rechecking for solution: 0 Report ID: b02ac054-910c-11e4-8264-74d02b29c5ad Report Status: 32770 Hashed bucket:
Log: 'Application' Date/Time: 31/12/2014 20:42:44
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: WindowsUpdateFailure2 Response: Not available Cab Id: 0 Problem signature: P1: 7.9.9600.17404 P2: 80246008 P3: F80F971D-E079-4216-B686-BF5D4412376B P4: Download P5: 101 P6: Unmanaged {9482F4B4-E343-43B6-B170-9A65BC822C77} P7: 80080005 P8: P9: P10: Attached files: C:\Windows\WindowsUpdate.log C:\Windows\SoftwareDistribution\ReportingEvents.log These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.9.9600.17404_c6a1415d359de4fa6506435f86d62717aa3ce75_00000000_cab_0d223179 Analysis symbol: Rechecking for solution: 0 Report ID: b02ac046-910c-11e4-8264-74d02b29c5ad Report Status: 32770 Hashed bucket:
Log: 'Application' Date/Time: 31/12/2014 20:42:44
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: WindowsUpdateFailure2 Response: Not available Cab Id: 0 Problem signature: P1: 7.9.9600.17404 P2: 80246008 P3: 2C167CE1-5104-4F84-A6A6-071A048F5E5D P4: Download P5: 101 P6: Unmanaged {9482F4B4-E343-43B6-B170-9A65BC822C77} P7: 80080005 P8: P9: P10: Attached files: C:\Windows\WindowsUpdate.log C:\Windows\SoftwareDistribution\ReportingEvents.log These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.9.9600.17404_c534ecbd99c1f6f8ce65b1534e472a7d64fb75_00000000_cab_0ece31b7 Analysis symbol: Rechecking for solution: 0 Report ID: b02ac051-910c-11e4-8264-74d02b29c5ad Report Status: 32770 Hashed bucket:
Log: 'Application' Date/Time: 31/12/2014 20:42:44
Type: Information Category: 0
Event: 1001 Source: Windows Error Reporting
Fault bucket , type 0 Event Name: WindowsUpdateFailure2 Response: Not available Cab Id: 0 Problem signature: P1: 7.9.9600.17404 P2: 80246008 P3: E316640A-63EE-4874-BCE4-65AE5E55AC49 P4: Download P5: 101 P6: Unmanaged {9482F4B4-E343-43B6-B170-9A65BC822C77} P7: 80080005 P8: P9: P10: Attached files: C:\Windows\WindowsUpdate.log C:\Windows\SoftwareDistribution\ReportingEvents.log These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.9.9600.17404_b9c6aca798ea3325a1fbdb923be1c083ff5aefc_00000000_cab_0c163169 Analysis symbol: Rechecking for solution: 0 Report ID: b02ac045-910c-11e4-8264-74d02b29c5ad Report Status: 32770 Hashed bucket:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 01/01/2015 20:28:58
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 31/12/2014 20:48:57
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 31/12/2014 18:47:54
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 31/12/2014 18:44:19
Type: Warning Category: 0
Event: 10010 Source: Microsoft-Windows-RestartManager
Application 'C:\tt\Guardian\GuardianMFC.exe' (pid 3044) cannot be restarted - Application SID does not match Conductor SID..
Log: 'Application' Date/Time: 31/12/2014 17:38:32
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 31/12/2014 14:47:19
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 31/12/2014 14:32:54
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 31/12/2014 14:32:18
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 31/12/2014 14:31:27
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 31/12/2014 14:12:28
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 31/12/2014 13:50:58
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 19/12/2014 12:39:18
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 18/12/2014 10:38:49
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 17/12/2014 09:06:42
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 16/12/2014 10:36:23
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 15/12/2014 04:46:00
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 11/12/2014 14:41:45
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 10/12/2014 09:29:16
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 05/12/2014 21:01:42
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
Log: 'Application' Date/Time: 05/12/2014 19:19:23
Type: Warning Category: 0
Event: 1 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Cisco AnyConnect VPN Client, from vendor Cisco) has the following problem: To function properly, Cisco AnyConnect VPN Client must be reinstalled after you upgrade Windows.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 03/11/2014 11:49:52
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: 01/11/2014 12:45:47
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: 01/01/2015 20:30:40
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 01/01/2015 20:28:40
Type: Error Category: 0
Event: 7024 Source: Service Control Manager
The Background Intelligent Transfer Service service terminated with the following service-specific error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Log: 'System' Date/Time: 01/01/2015 20:28:40
Type: Error Category: 0
Event: 16392 Source: Microsoft-Windows-Bits-Client
The BITS service failed to start. Error 0x80070422.
Log: 'System' Date/Time: 01/01/2015 20:28:40
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Network Connection Broker service terminated with the following error: A device attached to the system is not functioning.
Log: 'System' Date/Time: 01/01/2015 20:28:39
Type: Error Category: 0
Event: 7034 Source: Service Control Manager
The TT Guardian service terminated unexpectedly. It has done this 1 time(s).
Log: 'System' Date/Time: 01/01/2015 00:19:48
Type: Error Category: 0
Event: 7024 Source: Service Control Manager
The Background Intelligent Transfer Service service terminated with the following service-specific error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Log: 'System' Date/Time: 01/01/2015 00:19:48
Type: Error Category: 0
Event: 16392 Source: Microsoft-Windows-Bits-Client
The BITS service failed to start. Error 0x80070422.
Log: 'System' Date/Time: 31/12/2014 22:04:27
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 31/12/2014 22:02:27
Type: Error Category: 0
Event: 7024 Source: Service Control Manager
The Background Intelligent Transfer Service service terminated with the following service-specific error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Log: 'System' Date/Time: 31/12/2014 22:02:27
Type: Error Category: 0
Event: 16392 Source: Microsoft-Windows-Bits-Client
The BITS service failed to start. Error 0x80070422.
Log: 'System' Date/Time: 31/12/2014 22:02:27
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 31/12/2014 22:00:27
Type: Error Category: 0
Event: 7024 Source: Service Control Manager
The Background Intelligent Transfer Service service terminated with the following service-specific error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Log: 'System' Date/Time: 31/12/2014 22:00:27
Type: Error Category: 0
Event: 16392 Source: Microsoft-Windows-Bits-Client
The BITS service failed to start. Error 0x80070422.
Log: 'System' Date/Time: 31/12/2014 22:00:27
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 31/12/2014 21:58:27
Type: Error Category: 0
Event: 7024 Source: Service Control Manager
The Background Intelligent Transfer Service service terminated with the following service-specific error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Log: 'System' Date/Time: 31/12/2014 21:58:27
Type: Error Category: 0
Event: 16392 Source: Microsoft-Windows-Bits-Client
The BITS service failed to start. Error 0x80070422.
Log: 'System' Date/Time: 31/12/2014 21:58:27
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.
Log: 'System' Date/Time: 31/12/2014 21:56:27
Type: Error Category: 0
Event: 7024 Source: Service Control Manager
The Background Intelligent Transfer Service service terminated with the following service-specific error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Log: 'System' Date/Time: 31/12/2014 21:56:27
Type: Error Category: 0
Event: 16392 Source: Microsoft-Windows-Bits-Client
The BITS service failed to start. Error 0x80070422.
Log: 'System' Date/Time: 31/12/2014 21:56:27
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Information Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 01/01/2015 20:28:39
Type: Information Category: 1101
Event: 7001 Source: Microsoft-Windows-Winlogon
User Log-on Notification for Customer Experience Improvement Program
Log: 'System' Date/Time: 01/01/2015 20:28:38
Type: Information Category: 0
Event: 1 Source: Microsoft-Windows-Power-Troubleshooter
The system has returned from a low power state. Sleep Time: ?2015?-?01?-?01T01:26:50.205272500Z Wake Time: ?2015?-?01?-?01T20:28:35.083579900Z Wake Source: Unknown
Log: 'System' Date/Time: 01/01/2015 20:28:35
Type: Information Category: 0
Event: 33 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 01/01/2015 20:28:35
Type: Information Category: 0
Event: 27 Source: Microsoft-Windows-Kernel-Boot
The boot type was 0x1.
Log: 'System' Date/Time: 01/01/2015 20:28:35
Type: Information Category: 0
Event: 25 Source: Microsoft-Windows-Kernel-Boot
The boot menu policy was 0x1.
Log: 'System' Date/Time: 01/01/2015 20:28:35
Type: Information Category: 0
Event: 32 Source: Microsoft-Windows-Kernel-Boot
The bootmgr spent 0 ms waiting for user input.
Log: 'System' Date/Time: 01/01/2015 20:28:35
Type: Information Category: 0
Event: 18 Source: Microsoft-Windows-Kernel-Boot
There are 0x1 boot options on this system.
Log: 'System' Date/Time: 01/01/2015 20:28:35
Type: Information Category: 0
Event: 30 Source: Microsoft-Windows-Kernel-Boot
The firmware reported boot metrics.
Log: 'System' Date/Time: 01/01/2015 20:28:33
Type: Information Category: 0
Event: 1 Source: Microsoft-Windows-Kernel-General
The system time has changed to ?2015?-?01?-?01T20:28:33.500000000Z from ?2015?-?01?-?01T01:27:00.450110900Z. Change Reason: System time synchronized with the hardware clock.
Log: 'System' Date/Time: 01/01/2015 01:26:50
Type: Information Category: 64
Event: 42 Source: Microsoft-Windows-Kernel-Power
The system is entering sleep. Sleep Reason: Application API
Log: 'System' Date/Time: 01/01/2015 01:26:49
Type: Information Category: 1102
Event: 7002 Source: Microsoft-Windows-Winlogon
User Log-off Notification for Customer Experience Improvement Program
Log: 'System' Date/Time: 01/01/2015 01:26:49
Type: Information Category: 0
Event: 1074 Source: User32
The process C:\WINDOWS\system32\winlogon.exe (PC-PC) has initiated the power off of computer PC-PC on behalf of user PC-PC\PC for the following reason: No title for this reason could be found Reason Code: 0x500ff Shut-down Type: power off Comment:
Log: 'System' Date/Time: 01/01/2015 01:26:46
Type: Information Category: 0
Event: 1074 Source: User32
The process Explorer.EXE has initiated the power off of computer PC-PC on behalf of user PC-PC\PC for the following reason: Other (Unplanned) Reason Code: 0x0 Shut-down Type: power off Comment:
Log: 'System' Date/Time: 01/01/2015 00:00:00
Type: Information Category: 0
Event: 1 Source: Microsoft-Windows-Kernel-General
The system time has changed to ?2015?-?01?-?01T00:00:00.004827600Z from ?2015?-?01?-?01T00:00:00.004827600Z. Change Reason: System time adjusted to the new time zone.
Log: 'System' Date/Time: 31/12/2014 20:48:44
Type: Information Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) did not load: dam
Log: 'System' Date/Time: 31/12/2014 20:48:43
Type: Information Category: 1101
Event: 7001 Source: Microsoft-Windows-Winlogon
User Log-on Notification for Customer Experience Improvement Program
Log: 'System' Date/Time: 31/12/2014 20:48:42
Type: Information Category: 4
Event: 51046 Source: Microsoft-Windows-DHCPv6-Client
DHCPv6 client service is started
Log: 'System' Date/Time: 31/12/2014 20:48:42
Type: Information Category: 4
Event: 50036 Source: Microsoft-Windows-Dhcp-Client
DHCPv4 client service is started
Log: 'System' Date/Time: 31/12/2014 20:48:42
Type: Information Category: 0
Event: 6 Source: Microsoft-Windows-FilterManager
File System Filter 'luafv' (6.3, ?2014?-?02?-?22T12:14:25.000000000Z) has successfully loaded and registered with Filter Manager.
Log: 'System' Date/Time: 31/12/2014 20:48:40
Type: Information Category: 0
Event: 33 Source: e1iexpress
The event description cannot be found.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 01/01/2015 20:28:33
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 31/12/2014 20:56:29
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name
www.abit.com.tw timed out after none of the configured DNS servers responded.
Log: 'System' Date/Time: 31/12/2014 20:48:41
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: 31/12/2014 20:45:26
Type: Warning Category: 0
Event: 1073 Source: User32
The attempt by user PC-PC\PC to restart/shutdown computer PC-PC failed
Log: 'System' Date/Time: 31/12/2014 18:47:37
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: 31/12/2014 18:46:32
Type: Warning Category: 0
Event: 1073 Source: User32
The attempt by user PC-PC\PC to restart/shutdown computer PC-PC failed
Log: 'System' Date/Time: 31/12/2014 17:38:16
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: 31/12/2014 14:47:05
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: 31/12/2014 14:12:12
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: 31/12/2014 14:08:27
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 31/12/2014 14:08:24
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 31/12/2014 14:08:04
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 31/12/2014 14:07:00
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 31/12/2014 13:50:44
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 19/12/2014 12:39:04
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 18/12/2014 10:38:35
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 17/12/2014 09:06:28
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 16/12/2014 10:36:09
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 15/12/2014 13:12:43
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.
Log: 'System' Date/Time: 15/12/2014 04:45:46
Type: Warning Category: 0
Event: 27 Source: e1iexpress
The event description cannot be found.