Level Date and Time Source Event ID Task Category Error 26/04/2019 14:43:34 Application Error 1000 (100) "Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.17763.1, time stamp: 0x90f701bc Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000409 Fault offset: 0x0000000000000203 Faulting process id: 0x1e40 Faulting application start time: 0x01d4fc360a18f91f Faulting application path: C:\Windows\System32\MicrosoftEdgeCP.exe Faulting module path: unknown Report Id: 9490ae4c-14d7-458f-94a2-009f2cb4dcba Faulting package full name: Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe Faulting package-relative application ID: MicrosoftEdge" Error 26/04/2019 14:41:28 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 14:41:28 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 14:41:28 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 14:41:28 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 14:40:36 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-18305) 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." Error 26/04/2019 14:12:17 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 14:12:17 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 14:12:17 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 14:12:17 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:41 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:40 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:40 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:40 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:39 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:39 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:39 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:39 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:39 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:39 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:38 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:38 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:38 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:38 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:38 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:37 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:37 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:37 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:37 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:37 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:36 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:36 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:36 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 14:11:29 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-7626) 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." Warning 26/04/2019 14:11:12 Microsoft-Windows-User Device Registration 360 None "Windows Hello for Business provisioning will not be launched. Device is AAD joined ( AADJ or DJ++ ): Not Tested User has logged on with AAD credentials: No Windows Hello for Business policy is enabled: Not Tested Windows Hello for Business post-logon provisioning is enabled: Not Tested Local computer meets Windows hello for business hardware requirements: Not Tested User is not connected to the machine via Remote Desktop: Yes User certificate for on premise auth policy is enabled: Not Tested Machine is governed by none policy. See https://go.microsoft.com/fwlink/?linkid=832647 for more details." Error 26/04/2019 14:11:05 Microsoft-Windows-AppModel-Runtime 69 None Failed with 0x490 modifying AppModel Runtime status for package Microsoft.Windows.ContentDeliveryManager_10.0.17763.1_neutral_neutral_cw5n1h2txyewy for user Domain\User (current status = 0x0, desired status = 0x20). Error 26/04/2019 14:11:04 Microsoft-Windows-AppModel-Runtime 69 None Failed with 0x490 modifying AppModel Runtime status for package Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe for user Domain\User (current status = 0x0, desired status = 0x20). Error 26/04/2019 14:11:03 Microsoft-Windows-AppModel-Runtime 69 None Failed with 0x490 modifying AppModel Runtime status for package Microsoft.Windows.Cortana_1.11.5.17763_neutral_neutral_cw5n1h2txyewy for user Domain\User (current status = 0x0, desired status = 0x20). Error 26/04/2019 14:11:02 Microsoft-Windows-AppModel-Runtime 69 None Failed with 0x490 modifying AppModel Runtime status for package Microsoft.Windows.ShellExperienceHost_10.0.17763.1_neutral_neutral_cw5n1h2txyewy for user Domain\User (current status = 0x0, desired status = 0x20). Error 26/04/2019 14:11:00 Microsoft-Windows-AppModel-Runtime 69 None Failed with 0x490 modifying AppModel Runtime status for package Microsoft.Windows.CloudExperienceHost_10.0.17763.1_neutral_neutral_cw5n1h2txyewy for user Domain\User (current status = 0x0, desired status = 0x20). Error 26/04/2019 14:10:59 Microsoft-Windows-AppModel-Runtime 69 None Failed with 0x490 modifying AppModel Runtime status for package Microsoft.AAD.BrokerPlugin_1000.17763.1.0_neutral_neutral_cw5n1h2txyewy for user Domain\User (current status = 0x0, desired status = 0x20). Error 26/04/2019 14:10:53 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:52 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:51 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:50 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:49 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:48 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:48 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:47 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:46 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:46 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:45 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:45 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:44 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:44 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:43 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:43 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:43 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:43 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:42 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Error 26/04/2019 14:10:42 Microsoft-Windows-Kernel-EventTracing 2 Session "Session ""Circular Kernel Context Logger"" failed to start with the following error: 0xC0000035" Warning 26/04/2019 14:00:25 Microsoft-Windows-Winlogon 6006 None The winlogon notification subscriber took 600 second(s) to handle the notification event (EndShell). Warning 26/04/2019 13:51:25 Microsoft-Windows-Winlogon 6005 None The winlogon notification subscriber is taking long time to handle the notification event (EndShell). Warning 26/04/2019 13:51:02 LsaSrv 6038 None "Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server. NTLM is a weaker authentication mechanism. Please check: Which applications are using NTLM authentication? Are there configuration issues preventing the use of stronger authentication such as Kerberos authentication? If NTLM must be supported, is Extended Protection configured? Details on how to complete these checks can be found at http://go.microsoft.com/fwlink/?LinkId=225699." Error 26/04/2019 13:35:30 Microsoft-Windows-Kernel-EventTracing 3 Session "Session ""EventLog-AirSpaceChannel"" stopped due to the following error: 0xC0000188" Warning 26/04/2019 13:35:30 Microsoft-Windows-Kernel-EventTracing 4 Logging "The maximum file size for session ""EventLog-AirSpaceChannel"" has been reached. As a result, events might be lost (not logged) to file ""C:\windows\System32\Winevt\Logs\AirSpaceChannel.etl"". The maximum files size is currently set to 1048576 bytes." Error 26/04/2019 13:33:41 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 13:33:41 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 13:33:41 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 13:33:41 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 13:33:00 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-21862) 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." Error 26/04/2019 13:03:18 Service Control Manager 7000 None "The luafv service failed to start due to the following error: This driver has been blocked from loading" Warning 26/04/2019 13:02:54 Microsoft-Windows-Kernel-PnP 219 (212) The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000. Error 26/04/2019 13:03:19 Microsoft-Windows-Eventlog 1101 Event processing Audit events have been dropped by the transport. 0 Critical 26/04/2019 13:02:53 Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Warning 26/04/2019 13:02:19 Microsoft-Windows-Winlogon 6005 None The winlogon notification subscriber is taking long time to handle the notification event (EndShell). Error 26/04/2019 13:01:32 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 13:01:32 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 13:01:32 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 13:01:32 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 13:01:22 Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscDataProtection and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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." Error 26/04/2019 13:01:18 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 13:01:18 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 13:01:16 Microsoft-Windows-DistributedCOM 10010 None The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. Error 26/04/2019 13:01:15 Microsoft-Windows-DistributedCOM 10010 None The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. Error 26/04/2019 13:01:14 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 12:59:05 Service Control Manager 7000 None "The luafv service failed to start due to the following error: This driver has been blocked from loading" Warning 26/04/2019 12:58:40 Microsoft-Windows-Kernel-PnP 219 (212) The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000. Error 26/04/2019 12:59:06 Microsoft-Windows-Eventlog 1101 Event processing Audit events have been dropped by the transport. 0 Critical 26/04/2019 12:58:40 Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Warning 26/04/2019 12:01:28 Microsoft-Windows-Winlogon 6006 None The winlogon notification subscriber took 600 second(s) to handle the notification event (EndShell). Warning 26/04/2019 11:52:28 Microsoft-Windows-Winlogon 6005 None The winlogon notification subscriber is taking long time to handle the notification event (EndShell). Error 26/04/2019 11:30:12 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 11:30:12 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 11:30:12 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 11:30:12 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 11:30:10 Microsoft-Windows-Kernel-EventTracing 3 Session "Session ""Circular Kernel Context Logger"" stopped due to the following error: 0xC0000188" Warning 26/04/2019 11:30:10 Microsoft-Windows-Kernel-EventTracing 4 Logging "The maximum file size for session ""Circular Kernel Context Logger"" has been reached. As a result, events might be lost (not logged) to file ""C:\windows\system32\WDI\LogFiles\ShutdownCKCL.etl"". The maximum files size is currently set to 20971520 bytes." Error 26/04/2019 11:28:33 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-20642) 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." Error 26/04/2019 11:12:33 Microsoft-Windows-DistributedCOM 10001 None "Unable to start a DCOM Server: windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel as Unavailable/Unavailable. The error: ""0"" Happened while starting this command: ""C:\Windows\ImmersiveControlPanel\SystemSettings.exe"" -ServerName:microsoft.windows.immersivecontrolpanel" Error 26/04/2019 11:12:33 Microsoft-Windows-DistributedCOM 10010 None The server windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. Error 26/04/2019 11:07:38 Microsoft-Windows-Kernel-EventTracing 3 Session "Session ""EventLog-AirSpaceChannel"" stopped due to the following error: 0xC0000188" Warning 26/04/2019 11:07:38 Microsoft-Windows-Kernel-EventTracing 4 Logging "The maximum file size for session ""EventLog-AirSpaceChannel"" has been reached. As a result, events might be lost (not logged) to file ""C:\windows\System32\Winevt\Logs\AirSpaceChannel.etl"". The maximum files size is currently set to 1048576 bytes." Error 26/04/2019 11:06:51 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 11:06:51 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 11:06:51 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 11:06:51 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 11:05:55 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-20339) 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." Error 26/04/2019 09:56:29 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 09:56:29 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 09:56:29 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 09:56:29 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 09:55:30 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-21875) 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." Warning 26/04/2019 09:54:29 User32 1073 None The attempt by user Domain\User to restart/shutdown computer LIB-PC06 failed Warning 26/04/2019 09:54:29 Microsoft-Windows-Winlogon 6006 None The winlogon notification subscriber took 82 second(s) to handle the notification event (EndShell). Warning 26/04/2019 09:54:07 Microsoft-Windows-Winlogon 6005 None The winlogon notification subscriber is taking long time to handle the notification event (EndShell). Error 26/04/2019 09:53:30 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 09:53:30 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 09:53:30 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 09:53:30 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 09:53:04 Microsoft-Windows-DistributedCOM 10010 None The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:04 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:04 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:04 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:04 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:04 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:03 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:02 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:02 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:02 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:02 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:02 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:02 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:02 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:02 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:02 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:01 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:01 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:01 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:01 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:01 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:01 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:01 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:01 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:00 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:00 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:00 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:00 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:00 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:00 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:00 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:53:00 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:52:59 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:52:59 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:52:59 Microsoft-Windows-DistributedCOM 10010 None The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. Error 26/04/2019 09:52:37 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-21875) 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." Error 26/04/2019 09:51:59 Microsoft-Windows-User Profiles Service 1511 None Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off. Error 26/04/2019 09:51:59 Microsoft-Windows-User Profiles Service 1515 None Windows has backed up this user profile. Windows will automatically try to use the backup profile the next time this user logs on. Error 26/04/2019 09:50:19 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-20257) 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." Error 26/04/2019 09:50:02 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-20257) 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." Error 26/04/2019 09:41:17 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 09:41:17 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 09:41:16 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 09:41:16 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 09:40:22 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-20257) 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." Error 26/04/2019 09:26:31 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 09:26:31 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 09:26:31 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 09:26:31 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 09:26:14 Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscDataProtection and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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." Error 26/04/2019 09:25:24 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-20261) 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." Error 26/04/2019 09:23:00 Service Control Manager 7000 None "The luafv service failed to start due to the following error: This driver has been blocked from loading" Warning 26/04/2019 09:22:36 Microsoft-Windows-Kernel-PnP 219 (212) The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000. Error 26/04/2019 09:23:01 Microsoft-Windows-Eventlog 1101 Event processing Audit events have been dropped by the transport. 0 Critical 26/04/2019 09:22:36 Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Warning 26/04/2019 09:14:17 Microsoft-Windows-Winlogon 6005 None The winlogon notification subscriber is taking long time to handle the notification event (EndShell). Error 26/04/2019 09:08:35 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 09:08:35 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 09:08:35 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 09:08:35 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 09:07:58 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-21875) 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." Error 26/04/2019 08:36:34 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 08:36:34 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 08:36:34 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 08:36:34 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 08:36:00 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 08:36:00 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 08:36:00 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 08:36:00 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 08:32:44 Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID Windows.SecurityCenter.WscDataProtection and APPID Unavailable to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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." Error 26/04/2019 08:31:37 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 08:31:37 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 08:31:37 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 08:31:37 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 08:30:37 Service Control Manager 7000 None "The luafv service failed to start due to the following error: This driver has been blocked from loading" Warning 26/04/2019 08:30:14 Microsoft-Windows-Kernel-PnP 219 (212) The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000. Error 26/04/2019 08:30:39 Microsoft-Windows-Eventlog 1101 Event processing Audit events have been dropped by the transport. 0 Critical 26/04/2019 08:30:13 Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Warning 26/04/2019 08:22:45 Microsoft-Windows-Winlogon 6005 None The winlogon notification subscriber is taking long time to handle the notification event (EndShell). Error 26/04/2019 08:16:37 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 26/04/2019 08:16:37 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 26/04/2019 08:16:33 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 26/04/2019 08:16:29 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 26/04/2019 08:14:52 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-19301) 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." Warning 26/04/2019 07:15:45 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 26/04/2019 07:15:45 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 26/04/2019 07:07:26 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 26/04/2019 06:17:47 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 26/04/2019 05:29:45 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 26/04/2019 05:29:45 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 26/04/2019 05:13:34 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 26/04/2019 04:40:18 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 26/04/2019 04:13:55 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 26/04/2019 03:43:46 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 26/04/2019 03:43:46 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 26/04/2019 01:57:45 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 26/04/2019 01:57:45 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 26/04/2019 00:29:05 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 26/04/2019 00:11:45 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 26/04/2019 00:11:45 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 23:33:03 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 25/04/2019 22:56:35 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 25/04/2019 22:25:45 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 22:25:45 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 22:16:42 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 25/04/2019 20:39:46 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 20:39:46 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 19:29:10 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 25/04/2019 18:53:45 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 18:53:45 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 18:32:59 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 25/04/2019 18:07:54 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 25/04/2019 18:05:45 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 25/04/2019 17:32:29 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 25/04/2019 17:07:45 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 17:07:45 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 15:54:43 Microsoft-Windows-Winlogon 6006 None The winlogon notification subscriber took 600 second(s) to handle the notification event (EndShell). Warning 25/04/2019 15:45:43 Microsoft-Windows-Winlogon 6005 None The winlogon notification subscriber is taking long time to handle the notification event (EndShell). Error 25/04/2019 15:44:39 Microsoft-Windows-Kernel-EventTracing 3 Session "Session ""Circular Kernel Context Logger"" stopped due to the following error: 0xC0000188" Warning 25/04/2019 15:44:39 Microsoft-Windows-Kernel-EventTracing 4 Logging "The maximum file size for session ""Circular Kernel Context Logger"" has been reached. As a result, events might be lost (not logged) to file ""C:\windows\system32\WDI\LogFiles\ShutdownCKCL.etl"". The maximum files size is currently set to 20971520 bytes." Error 25/04/2019 15:34:03 Application Error 1000 (100) "Faulting application name: Notebook.exe, version: 11.4.564.0, time stamp: 0x52967b2c Faulting module name: QtCore4.dll, version: 4.8.4.0, time stamp: 0x515b176e Exception code: 0xc0000005 Fault offset: 0x001127a6 Faulting process id: 0x19b8 Faulting application start time: 0x01d4fb73a3701562 Faulting application path: C:\Program Files (x86)\SMART Technologies\Education Software\Notebook.exe Faulting module path: C:\windows\WinSxS\x86_smarttech.qt.vc100.4.8_37a8c5fef6a21868_1.0.2.0_none_fc4a69fd708c7cb3\QtCore4.dll Report Id: 2cc55a9f-ce20-4043-b648-d79eb6b1a44f Faulting package full name: Faulting package-relative application ID: " Error 25/04/2019 15:27:14 Application Error 1000 (100) "Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.17763.1, time stamp: 0x90f701bc Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000409 Fault offset: 0x0000000000000203 Faulting process id: 0x164 Faulting application start time: 0x01d4fb72f916fa7f Faulting application path: C:\Windows\System32\MicrosoftEdgeCP.exe Faulting module path: unknown Report Id: 9038b8fa-7ca4-44de-ad24-46d32c14a0f8 Faulting package full name: Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe Faulting package-relative application ID: MicrosoftEdge" Warning 25/04/2019 15:25:49 LsaSrv 6038 None "Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server. NTLM is a weaker authentication mechanism. Please check: Which applications are using NTLM authentication? Are there configuration issues preventing the use of stronger authentication such as Kerberos authentication? If NTLM must be supported, is Extended Protection configured? Details on how to complete these checks can be found at http://go.microsoft.com/fwlink/?LinkId=225699." Warning 25/04/2019 15:21:45 Group Policy Files 4098 (2) The computer 'ultravnc.ini' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Warning 25/04/2019 15:21:45 Group Policy Files 4098 (2) The computer 'settings' preference item in the 'Default PC Policy (ALL) {B940C3D1-0EFE-40A0-8D87-258E2733EFF1}' Group Policy Object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed. Error 25/04/2019 15:01:32 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 25/04/2019 15:01:32 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 25/04/2019 15:01:32 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 25/04/2019 15:01:32 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 25/04/2019 15:00:41 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\Use SID (S-1-5-21-2069765483-1425354119-1238779560-20335) 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." Error 25/04/2019 14:44:37 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 25/04/2019 14:44:37 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 25/04/2019 14:44:37 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 25/04/2019 14:44:34 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 25/04/2019 14:44:05 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-19283) 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." Error 25/04/2019 14:43:54 Application Error 1000 (100) "Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.17763.1, time stamp: 0x90f701bc Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000409 Fault offset: 0x0000000000000203 Faulting process id: 0x22ec Faulting application start time: 0x01d4fb6ce88ed3d6 Faulting application path: C:\Windows\System32\MicrosoftEdgeCP.exe Faulting module path: unknown Report Id: 6d76563b-5c91-4b80-82b5-a2e3851ad1ee Faulting package full name: Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe Faulting package-relative application ID: MicrosoftEdge" Warning 25/04/2019 14:42:06 Microsoft-Windows-Time-Service 129 None NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1) Warning 25/04/2019 14:42:06 Microsoft-Windows-Time-Service 129 None NtpClient was unable to set a domain peer to use as a time source because of discovery error. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry is not found. (0x800706E1) Warning 25/04/2019 14:42:05 e1cexpress 27 None "Intel(R) 82579LM Gigabit Network Connection Network link is disconnected. " Warning 25/04/2019 14:41:20 Microsoft-Windows-TerminalServices-ServerUSBDevices 36 None Redirection of additional supported devices is disabled by policy. Warning 25/04/2019 14:41:20 Microsoft-Windows-TerminalServices-PnPDevices 36 None Redirection of additional supported devices is disabled by policy. Warning 25/04/2019 14:41:20 User32 1073 None The attempt by user Domain\User to restart/shutdown computer LIB-PC06 failed Warning 25/04/2019 14:41:20 Microsoft-Windows-Winlogon 6006 None The winlogon notification subscriber took 216 second(s) to handle the notification event (EndShell). Warning 25/04/2019 14:38:43 Microsoft-Windows-Winlogon 6005 None The winlogon notification subscriber is taking long time to handle the notification event (EndShell). Error 25/04/2019 14:26:29 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-19284) 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." Warning 25/04/2019 14:26:17 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Error 25/04/2019 14:07:59 Application Error 1000 (100) "Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.17763.1, time stamp: 0x90f701bc Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000409 Fault offset: 0x0000000000000203 Faulting process id: 0x20b8 Faulting application start time: 0x01d4fb67e68d36aa Faulting application path: C:\Windows\System32\MicrosoftEdgeCP.exe Faulting module path: unknown Report Id: 0f641155-d662-4a96-9af9-9d5212e423ad Faulting package full name: Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe Faulting package-relative application ID: MicrosoftEdge" Error 25/04/2019 14:07:40 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 25/04/2019 14:07:40 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 25/04/2019 14:07:40 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 25/04/2019 14:07:40 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2 Error 25/04/2019 14:07:26 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-19284) 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." Error 25/04/2019 14:06:50 Microsoft-Windows-DistributedCOM 10016 None "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 Domain\User SID (S-1-5-21-2069765483-1425354119-1238779560-19284) 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." Warning 25/04/2019 13:59:34 MEIx64 1 None The Intel(R) Management Engine Interface is being reset. Warning 25/04/2019 13:58:26 Microsoft-Windows-Winlogon 6006 None The winlogon notification subscriber took 600 second(s) to handle the notification event (EndShell). Warning 25/04/2019 13:49:26 Microsoft-Windows-Winlogon 6005 None The winlogon notification subscriber is taking long time to handle the notification event (EndShell). Error 25/04/2019 13:47:30 Microsoft-Windows-DistributedCOM 10000 None "Unable to start a DCOM Server: {71DCE5D6-4B57-496B-AC21-CD5B54EB93FD}. The error: ""0"" Happened while starting this command: C:\Users\hodgettsn\AppData\Local\Microsoft\OneDrive\19.043.0304.0007\FileCoAuth.exe -Embedding" Warning 25/04/2019 13:47:30 Microsoft-Windows-SoftwareRestrictionPolicies 866 None Access to C:\Users\hodgettsn\AppData\Local\Microsoft\OneDrive\19.043.0304.0007\FileCoAuth.exe has been restricted by your Administrator by location with policy rule {8193AA50-2BC7-4C33-A361-2581BC4988A1} placed on path c:\users. Error 25/04/2019 13:47:30 Microsoft-Windows-DistributedCOM 10000 None "Unable to start a DCOM Server: {71DCE5D6-4B57-496B-AC21-CD5B54EB93FD}. The error: ""0"" Happened while starting this command: C:\Users\hodgettsn\AppData\Local\Microsoft\OneDrive\19.043.0304.0007\FileCoAuth.exe -Embedding" Warning 25/04/2019 13:47:30 Microsoft-Windows-SoftwareRestrictionPolicies 866 None Access to C:\Users\hodgettsn\AppData\Local\Microsoft\OneDrive\19.043.0304.0007\FileCoAuth.exe has been restricted by your Administrator by location with policy rule {8193AA50-2BC7-4C33-A361-2581BC4988A1} placed on path c:\users. Error 25/04/2019 13:43:04 Microsoft-Windows-Kernel-EventTracing 3 Session "Session ""EventLog-AirSpaceChannel"" stopped due to the following error: 0xC0000188" Warning 25/04/2019 13:43:04 Microsoft-Windows-Kernel-EventTracing 4 Logging "The maximum file size for session ""EventLog-AirSpaceChannel"" has been reached. As a result, events might be lost (not logged) to file ""C:\windows\System32\Winevt\Logs\AirSpaceChannel.etl"". The maximum files size is currently set to 1048576 bytes." Error 25/04/2019 13:41:27 Microsoft-Windows-User Device Registration 304 None "Automatic registration failed at join phase. Exit code: Unknown HResult Error code: 0x801c0021 Server error: Tenant type: undefined Registration type: undefined Debug Output: joinMode: Join drsInstance: undefined registrationType: undefined tenantType: undefined tenantId: undefined configLocation: undefined errorPhase: discover adalCorrelationId: undefined adalLog: undefined adalResponseCode: 0x0 " Error 25/04/2019 13:41:27 Microsoft-Windows-User Device Registration 309 None Failed to discover the Azure AD DRS service. Exit code: Unknown HResult Error code: 0x801c0021. Error 25/04/2019 13:41:27 Microsoft-Windows-User Device Registration 201 None "The discovery operation callback failed with exit code: Unknown HResult Error code: 0x80072ee2. The server returned HTTP status: 0. Server response was: " Error 25/04/2019 13:41:26 Microsoft-Windows-User Device Registration 233 None The WinHTTP callback function failed. WINHTTP_STATUS_CALLBACK status code: 2097152 (WINHTTP_CALLBACK_STATUS_REQUEST_ERROR). Error: Unknown HResult Error code: 0x80072ee2