Vino's Event Viewer v01c run on Windows 7 in English Report run at 29/08/2020 1:59:56 PM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Critical Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 29/08/2020 5:54:20 AM Type: Error Category: 3 Event: 455 Source: ESENT svchost (12140,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log. Log: 'Application' Date/Time: 29/08/2020 5:35:40 AM Type: Error Category: 3 Event: 455 Source: ESENT svchost (1148,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log. Log: 'Application' Date/Time: 29/08/2020 5:29:30 AM Type: Error Category: 3 Event: 455 Source: ESENT svchost (3340,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log. Log: 'Application' Date/Time: 29/08/2020 5:09:10 AM Type: Error Category: 0 Event: 0 Source: HP Comm Recovery Failed in handling the PowerEvent. The error that occurred was: System.IO.IOException: The process cannot access the file 'C:\Windows\Temp\signtool.exe' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at _HPCommRecovery.Tools.Signtool.ExtractSignTool() at _HPCommRecovery.Tools.Signtool.Verify(String arg) at _HPCommRecovery.HPAHAgent.CallAgent() at _HPCommRecovery.AppSession..ctor(DateTime Current, String LogPath) at _HPCommRecovery.HPAHLogger.NewSession() at _HPCommRecovery..... Log: 'Application' Date/Time: 27/08/2020 1:03:07 AM Type: Error Category: 100 Event: 1000 Source: Application Error Faulting application name: taskhostw.exe, version: 10.0.18362.387, time stamp: 0x5fefc7f9 Faulting module name: amdihk64.dll_unloaded, version: 1.0.0.0, time stamp: 0x5bc5e1ff Exception code: 0xc0000005 Fault offset: 0x0000000000002fbf Faulting process id: 0x1520 Faulting application start time: 0x01d67c0daae458f5 Faulting application path: C:\WINDOWS\system32\taskhostw.exe Faulting module path: amdihk64.dll Report Id: 9d583f4f-e10c-44b3-ab18-a402d5f2b1cd Faulting package full name: Faulting package-relative application ID: Log: 'Application' Date/Time: 27/08/2020 12:56:05 AM Type: Error Category: 0 Event: 1552 Source: Microsoft-Windows-User Profiles Service User hive is loaded by another process (Registry Lock) Process name: C:\Windows\System32\svchost.exe, PID: 6020, ProfSvc PID: 2232. Log: 'Application' Date/Time: 21/08/2020 6:57:18 AM Type: Error Category: 0 Event: 0 Source: HP Comm Recovery Failed in handling the PowerEvent. The error that occurred was: System.IO.IOException: The process cannot access the file 'C:\Windows\Temp\signtool.exe' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at _HPCommRecovery.Tools.Signtool.ExtractSignTool() at _HPCommRecovery.Tools.Signtool.Verify(String arg) at _HPCommRecovery.HPAHAgent.CallAgent() at _HPCommRecovery.AppSession..ctor(DateTime Current, String LogPath) at _HPCommRecovery.HPAHLogger.NewSession() at _HPCommRecovery..... Log: 'Application' Date/Time: 19/08/2020 5:26:45 AM Type: Error Category: 0 Event: 0 Source: HP Comm Recovery Failed in handling the PowerEvent. The error that occurred was: System.IO.IOException: The process cannot access the file 'C:\Windows\Temp\signtool.exe' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at _HPCommRecovery.Tools.Signtool.ExtractSignTool() at _HPCommRecovery.Tools.Signtool.Verify(String arg) at _HPCommRecovery.HPAHAgent.CallAgent() at _HPCommRecovery.AppSession..ctor(DateTime Current, String LogPath) at _HPCommRecovery.HPAHLogger.NewSession() at _HPCommRecovery..... Log: 'Application' Date/Time: 19/08/2020 5:26:13 AM Type: Error Category: 0 Event: 0 Source: HP Comm Recovery Failed in handling the PowerEvent. The error that occurred was: System.UnauthorizedAccessException: Access to the path 'C:\Windows\Temp\signtool.exe' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalDelete(String path, Boolean checkHost) at _HPCommRecovery.Tools.Signtool.Verify(String arg) at _HPCommRecovery.HPAHAgent.CallAgent() at _HPCommRecovery.AppSession..ctor(DateTime Current, String LogPath) at _HPCommRecovery.HPAHLogger.NewSession() at _HPCommRecovery.HPCommRecovery.OnPowerEvent(PowerBroadcastStatus powerStatus) at System.ServiceProcess.ServiceBase.DeferredPowerEvent(Int32 eventType, IntPtr eventData). Log: 'Application' Date/Time: 15/08/2020 4:43:46 AM Type: Error Category: 100 Event: 1000 Source: Application Error Faulting application name: SystemSettings.exe, version: 10.0.18362.628, time stamp: 0x066bf1a5 Faulting module name: fhsettingsprovider.dll, version: 10.0.18362.959, time stamp: 0xbc6f9686 Exception code: 0xc0000005 Fault offset: 0x0000000000007aee Faulting process id: 0x2774 Faulting application start time: 0x01d672acacfc7c3e Faulting application path: C:\Windows\ImmersiveControlPanel\SystemSettings.exe Faulting module path: C:\Windows\System32\fhsettingsprovider.dll Report Id: 94807288-67ac-4a4b-a932-36deb11258b9 Faulting package full name: windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: microsoft.windows.immersivecontrolpanel Log: 'Application' Date/Time: 15/08/2020 2:19:04 AM Type: Error Category: 0 Event: 0 Source: HP Comm Recovery Failed in handling the PowerEvent. The error that occurred was: System.IO.IOException: The process cannot access the file 'C:\Windows\Temp\signtool.exe' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at _HPCommRecovery.Tools.Signtool.ExtractSignTool() at _HPCommRecovery.Tools.Signtool.Verify(String arg) at _HPCommRecovery.HPAHAgent.CallAgent() at _HPCommRecovery.AppSession..ctor(DateTime Current, String LogPath) at _HPCommRecovery.HPAHLogger.NewSession() at _HPCommRecovery..... Log: 'Application' Date/Time: 12/08/2020 6:27:55 AM Type: Error Category: 0 Event: 31 Source: Microsoft-Windows-Spell-Checking Failed to update Added Words user custom wordlist: The process cannot access the file because it is being used by another process.. Spell checking will remain available, but this user wordlist will not be updated. Log: 'Application' Date/Time: 12/08/2020 1:27:10 AM Type: Error Category: 0 Event: 0 Source: HP Comm Recovery Failed in handling the PowerEvent. The error that occurred was: System.IO.IOException: The process cannot access the file 'C:\Windows\Temp\signtool.exe' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at _HPCommRecovery.Tools.Signtool.ExtractSignTool() at _HPCommRecovery.Tools.Signtool.Verify(String arg) at _HPCommRecovery.HPAHAgent.CallAgent() at _HPCommRecovery.AppSession..ctor(DateTime Current, String LogPath) at _HPCommRecovery.HPAHLogger.NewSession() at _HPCommRecovery..... Log: 'Application' Date/Time: 11/08/2020 2:03:51 AM Type: Error Category: 101 Event: 1002 Source: Application Hang The program SearchUI.exe version 10.0.18362.752 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: 12c8 Start Time: 01d66f836b02917e Termination Time: 4294967295 Application Path: C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe Report Id: 49adb6f9-4430-4b06-bec4-39beb39e6aa1 Faulting package full name: Microsoft.Windows.Cortana_1.13.0.18362_neutral_neutral_cw5n1h2txyewy Faulting package-relative application ID: CortanaUI Hang type: Cross-thread Log: 'Application' Date/Time: 11/08/2020 2:01:14 AM Type: Error Category: 0 Event: 0 Source: HP Comm Recovery Failed in handling the PowerEvent. The error that occurred was: System.IO.IOException: The process cannot access the file 'C:\Windows\Temp\signtool.exe' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at _HPCommRecovery.Tools.Signtool.ExtractSignTool() at _HPCommRecovery.Tools.Signtool.Verify(String arg) at _HPCommRecovery.HPAHAgent.CallAgent() at _HPCommRecovery.AppSession..ctor(DateTime Current, String LogPath) at _HPCommRecovery.HPAHLogger.NewSession() at _HPCommRecovery..... Log: 'Application' Date/Time: 09/08/2020 7:45:29 AM Type: Error Category: 0 Event: 0 Source: HP Comm Recovery Failed in handling the PowerEvent. The error that occurred was: System.IO.IOException: The process cannot access the file 'C:\Windows\Temp\signtool.exe' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at _HPCommRecovery.Tools.Signtool.ExtractSignTool() at _HPCommRecovery.Tools.Signtool.Verify(String arg) at _HPCommRecovery.HPAHAgent.CallAgent() at _HPCommRecovery.AppSession..ctor(DateTime Current, String LogPath) at _HPCommRecovery.HPAHLogger.NewSession() at _HPCommRecovery..... Log: 'Application' Date/Time: 05/08/2020 1:38:25 AM Type: Error Category: 0 Event: 0 Source: HP Comm Recovery Failed in handling the PowerEvent. The error that occurred was: System.IO.IOException: The process cannot access the file 'C:\Windows\Temp\signtool.exe' because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at _HPCommRecovery.Tools.Signtool.ExtractSignTool() at _HPCommRecovery.Tools.Signtool.Verify(String arg) at _HPCommRecovery.HPAHAgent.CallAgent() at _HPCommRecovery.AppSession..ctor(DateTime Current, String LogPath) at _HPCommRecovery.HPAHLogger.NewSession() at _HPCommRecovery..... Log: 'Application' Date/Time: 04/08/2020 2:54:27 AM Type: Error Category: 3 Event: 455 Source: ESENT svchost (10572,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log. Log: 'Application' Date/Time: 04/08/2020 1:54:25 AM Type: Error Category: 3 Event: 455 Source: ESENT svchost (7324,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log. Log: 'Application' Date/Time: 04/08/2020 1:43:40 AM Type: Error Category: 3 Event: 455 Source: ESENT svchost (10108,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'Application' Log - Warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'Application' Date/Time: 30/07/2020 10:47:41 AM Type: Warning Category: 1 Event: 32068 Source: Microsoft Fax The outgoing routing rule is not valid because it cannot find a valid device. Check the routing rule configuration. Country/region code: '*' Area code: '*' Log: 'Application' Date/Time: 30/07/2020 10:47:41 AM Type: Warning Category: 1 Event: 32026 Source: Microsoft Fax Fax Service failed to initialize any assigned fax devices. No faxes can be sent or received until a fax device is installed. Log: 'Application' Date/Time: 27/07/2020 1:21:27 AM Type: Warning Category: 0 Event: 6006 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber took 72 second(s) to handle the notification event (CreateSession). Log: 'Application' Date/Time: 27/07/2020 1:21:14 AM Type: Warning Category: 0 Event: 6005 Source: Microsoft-Windows-Winlogon The winlogon notification subscriber is taking long time to handle the notification event (CreateSession). Log: 'Application' Date/Time: 14/06/2020 5:26:43 AM Type: Warning Category: 7 Event: 508 Source: ESENT svchost (17552,D,0) Unistore: A request to write to the file "C:\Users\61467\AppData\Local\Comms\UnistoreDB\store.vol" at offset 159744 (0x0000000000027000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (21 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 23/05/2020 5:09:13 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: 23/05/2020 5:09:13 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: 23/05/2020 5:09:13 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: 23/05/2020 5:09:12 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: 23/05/2020 5:09:12 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: 23/05/2020 5:09:12 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: 20/05/2020 1:44:27 AM Type: Warning Category: 7 Event: 508 Source: ESENT svchost (17544,D,0) Unistore: A request to write to the file "C:\Users\61467\AppData\Local\Comms\UnistoreDB\store.vol" at offset 1658880 (0x0000000000195000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (16 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Log: 'Application' Date/Time: 28/03/2020 6:24:42 AM Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, DSCCoreProviders, has been registered in the Windows Management Instrumentation namespace ROOT\Microsoft\Windows\DesiredStateConfiguration 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: 28/03/2020 6:24:42 AM Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, EventTracingManagement, has been registered in the Windows Management Instrumentation namespace ROOT\Microsoft\Windows\EventTracingManagement 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: 28/03/2020 6:24:42 AM Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, EventTracingManagement, has been registered in the Windows Management Instrumentation namespace ROOT\Microsoft\Windows\EventTracingManagement 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: 28/03/2020 6:24:42 AM Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, EventTracingManagement, has been registered in the Windows Management Instrumentation namespace ROOT\Microsoft\Windows\EventTracingManagement 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: 28/03/2020 6:24:38 AM Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, WsmAgent, has been registered in the Windows Management Instrumentation namespace ROOT\Microsoft\Windows\winrm 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: 28/03/2020 6:24:38 AM Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, WsmAgent, has been registered in the Windows Management Instrumentation namespace ROOT\Microsoft\Windows\winrm 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: 28/03/2020 6:24:34 AM Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, ProfileAssociationProviderInterop, has been registered in the Windows Management Instrumentation namespace ROOT\Interop 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: 28/03/2020 6:24:34 AM Type: Warning Category: 0 Event: 63 Source: Microsoft-Windows-WMI A provider, ProfileAssociationProviderInterop, has been registered in the Windows Management Instrumentation namespace ROOT\Interop 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.