Level Date and Time Source Event ID Task Category Warning 12/5/2025 10:19:05 PM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 12/5/2025 10:17:37 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 12/5/2025 10:16:43 PM Service Control Manager 7023 None "The Function Discovery Resource Publication service terminated with the following error: The requested address is not valid in its context." Warning 12/5/2025 10:16:40 PM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 12/5/2025 10:16:40 PM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Information 12/5/2025 10:16:40 PM Microsoft-Windows-Power-Troubleshooter 1 None "The system has returned from a low power state. Sleep Time: ‎2025‎-‎12‎-‎06T06:16:19.200675400Z Wake Time: ‎2025‎-‎12‎-‎06T06:16:39.377076500Z Wake Source: Power Button" Warning 12/5/2025 10:16:40 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Warning 12/5/2025 10:16:39 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Information 12/5/2025 10:16:38 PM Microsoft-Windows-Kernel-Power 131 (33) Firmware S3 times. ResumeCount: 2, FullResume: 159, AverageResume: 160 Information 12/5/2025 10:16:38 PM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎12‎-‎06T06:16:38.500000000Z from ‎2025‎-‎12‎-‎06T06:16:22.853950500Z. Change Reason: System time synchronized with the hardware clock. Process: '' (PID 4)." Information 12/5/2025 10:16:22 PM Microsoft-Windows-Kernel-Power 107 (102) The system has resumed from sleep. Information 12/5/2025 10:16:22 PM Microsoft-Windows-Kernel-Power 42 (64) "The system is entering sleep. Sleep Reason: Button or Lid" Warning 12/5/2025 10:12:18 PM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 12/5/2025 10:11:27 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Warning 12/5/2025 10:11:18 PM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 12/5/2025 10:11:10 PM Microsoft-Windows-UserPnp 20003 (7005) Driver Management has concluded the process to add Service WUDFWpdFs for Device Instance ID SWD\WPDBUSENUM\_??_SCSI#DISK&VEN__USB&PROD__SANDISK_3.2GEN1#6&48D9F7&0&000000#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B} with the following status: 0. Information 12/5/2025 10:11:10 PM Microsoft-Windows-DriverFrameworks-UserMode 10100 Installation or update of device drivers. The driver package installation has succeeded. Information 12/5/2025 10:11:10 PM Microsoft-Windows-DriverFrameworks-UserMode 10002 Installation or update of device drivers. The UMDF service WpdFs (CLSID {112de495-ac4c-46f8-b663-6a4266c53313}) was upgraded. It requires framework version 2.31.0 or higher. Information 12/5/2025 10:11:10 PM Microsoft-Windows-DriverFrameworks-UserMode 10000 Installation or update of device drivers. A driver package which uses user-mode driver framework version 2.31.0 is being installed on device SWD\WPDBUSENUM\_??_SCSI#DISK&VEN__USB&PROD__SANDISK_3.2GEN1#6&48D9F7&0&000000#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}. Warning 12/5/2025 10:11:10 PM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 12/5/2025 10:11:11 PM Microsoft-Windows-WPDClassInstaller 24579 Driver Post-Install Configuration Autoplay registration was skipped for device %1. Information 12/5/2025 10:11:11 PM Microsoft-Windows-WPDClassInstaller 24577 Driver Post-Install Configuration Media player and imaging program compatibility layers were successfully registered for device %1. Layer bits %2 were requested, layer bits %3 were registered. Information 12/5/2025 10:11:10 PM Microsoft-Windows-WPDClassInstaller 24576 Driver Installation Drivers were successfully installed for device WPD Device. Error 12/5/2025 10:11:09 PM Ntfs 55 None "A corruption was discovered in the file system structure on volume E:. The exact nature of the corruption is unknown. The file system structures need to be scanned online. " Information 12/5/2025 10:07:54 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Warning 12/5/2025 10:07:04 PM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Warning 12/5/2025 10:06:47 PM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Warning 12/5/2025 10:06:45 PM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Error 12/5/2025 10:06:15 PM Microsoft-Windows-TPM-WMI 1801 None "Secure Boot CA/keys need to be updated. This device signature information is included here. DeviceAttributes: BaseBoardManufacturer:INTEL Corporation;FirmwareManufacturer:American Megatrends Inc.;FirmwareVersion:5.6.5;OEMModelNumber:To be filled by O.E.M.;OEMModelBaseBoard:CRESCENTBAY;OEMModelSystemFamily:To be filled by O.E.M.;OEMManufacturerName:To be filled by O.E.M.;OEMModelSKU:To be filled by O.E.M.;OSArchitecture:amd64; BucketId: 3172bfdf51002a90ec09ce6a4c3dd16df4a8a200aa84b1d0136a4916f76764e2 BucketConfidenceLevel: UpdateType: 0 HResult: The operation completed successfully." Warning 12/5/2025 10:04:39 PM Microsoft-Windows-Time-Service 134 None NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9) Warning 12/5/2025 10:04:37 PM Microsoft-Windows-Time-Service 134 None NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9) Error 12/5/2025 10:04:36 PM Service Control Manager 7023 None "The Function Discovery Resource Publication service terminated with the following error: The requested address is not valid in its context." Information 12/5/2025 10:04:35 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.LockApp_cw5n1h2txyewy\Settings\settings.dat was cleared updating 3 keys and creating 1 modified pages. Warning 12/5/2025 10:04:33 PM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 12/5/2025 10:04:33 PM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Information 12/5/2025 10:04:32 PM Microsoft-Windows-Power-Troubleshooter 1 None "The system has returned from a low power state. Sleep Time: ‎2025‎-‎12‎-‎06T06:04:24.215579800Z Wake Time: ‎2025‎-‎12‎-‎06T06:04:32.368200600Z Wake Source: Power Button" Warning 12/5/2025 10:04:32 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Warning 12/5/2025 10:04:32 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Warning 12/5/2025 10:04:32 PM Microsoft-Windows-Time-Service 134 None NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9) Information 12/5/2025 10:04:31 PM Microsoft-Windows-Kernel-Power 131 (33) Firmware S3 times. ResumeCount: 1, FullResume: 162, AverageResume: 162 Information 12/5/2025 10:04:31 PM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎12‎-‎06T06:04:31.500000000Z from ‎2025‎-‎12‎-‎06T06:04:26.244670400Z. Change Reason: System time synchronized with the hardware clock. Process: '' (PID 4)." Information 12/5/2025 10:04:26 PM Microsoft-Windows-Kernel-Power 107 (102) The system has resumed from sleep. Warning 12/5/2025 10:04:25 PM Microsoft-Windows-Time-Service 134 None NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9) Information 12/5/2025 10:04:25 PM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎12‎-‎06T06:04:24.500000000Z from ‎2025‎-‎12‎-‎06T06:04:25.590320400Z. Change Reason: System time synchronized with the hardware clock. Process: '' (PID 4)." Information 12/5/2025 10:04:25 PM Microsoft-Windows-Kernel-Power 42 (64) "The system is entering sleep. Sleep Reason: Button or Lid" Information 12/5/2025 10:03:34 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\Settings\settings.dat was cleared updating 12009 keys and creating 368 modified pages. Warning 12/5/2025 10:03:24 PM 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.SecurityAppBroker 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." Warning 12/5/2025 10:03:24 PM 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." Warning 12/5/2025 10:03:24 PM 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.WscBrokerManager 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." Warning 12/5/2025 10:02:26 PM Microsoft-Windows-Time-Service 134 None NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9) Warning 12/5/2025 10:02:26 PM Microsoft-Windows-Time-Service 134 None NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9) Information 12/5/2025 10:02:26 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Warning 12/5/2025 10:02:19 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 12/5/2025 10:02:19 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 12/5/2025 10:02:19 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 12/5/2025 10:02:19 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Information 12/5/2025 10:02:12 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.YourPhone_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\d4be7e4a3deb5b23_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Information 12/5/2025 10:02:12 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.YourPhone_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 46 keys and creating 5 modified pages. Information 12/5/2025 10:01:59 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/5/2025 10:01:53 PM Service Control Manager 7045 None "A service was installed in the system. Service Name: Microsoft Defender Core Service Service File Name: ""C:\ProgramData\Microsoft\Windows Defender\Platform\4.18.25100.9008-0\MpDefenderCoreService.exe"" Service Type: user mode service Service Start Type: auto start Service Account: LocalSystem" Information 12/5/2025 10:01:39 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Settings\settings.dat was cleared updating 5 keys and creating 1 modified pages. Information 12/5/2025 10:01:35 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\microsoft.windows.search_cw5n1h2txyewy\AC\GEH\POF.dat was cleared updating 6 keys and creating 1 modified pages. Information 12/5/2025 10:01:34 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.Search_cw5n1h2txyewy\Settings\settings.dat was cleared updating 36 keys and creating 7 modified pages. Warning 12/5/2025 10:01:26 PM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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 12/5/2025 10:01:26 PM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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 12/5/2025 10:01:26 PM Service Control Manager 7023 None "The Function Discovery Resource Publication service terminated with the following error: The requested address is not valid in its context." Information 12/5/2025 10:01:23 PM Service Control Manager 7026 None "The following boot-start or system-start driver(s) did not load: dam" Error 12/5/2025 10:01:19 PM Service Control Manager 7034 None The MediaMTX service terminated unexpectedly. It has done this 1 time(s). Error 12/5/2025 10:01:19 PM Service Control Manager 7024 None "The MediaMTX service terminated with the following service-specific error: The system cannot find the path specified." Information 12/5/2025 10:01:18 PM Microsoft-Windows-Winlogon 7001 (1101) User Logon Notification for Customer Experience Improvement Program Information 12/5/2025 10:01:17 PM Microsoft-Windows-WLAN-AutoConfig 4000 None "WLAN AutoConfig service has successfully started. " Information 12/5/2025 10:01:14 PM Microsoft-Windows-DHCPv6-Client 51046 Service State Event DHCPv6 client service is started Information 12/5/2025 10:01:14 PM Microsoft-Windows-Dhcp-Client 50103 Service State Event DHCPv4 client registered for shutdown notification Information 12/5/2025 10:01:14 PM Microsoft-Windows-Dhcp-Client 50036 Service State Event DHCPv4 client service is started Information 12/5/2025 10:01:14 PM Microsoft-Windows-FilterManager 6 None File System Filter 'bindflt' (10.0, ‎2091‎-‎04‎-‎15T15:55:03.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:14 PM Microsoft-Windows-FilterManager 6 None File System Filter 'storqosflt' (10.0, ‎2038‎-‎12‎-‎03T01:18:20.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:14 PM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:14 PM Microsoft-Windows-FilterManager 1 None File System Filter 'CldFlt' (Version 10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) unloaded successfully. Information 12/5/2025 10:01:14 PM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:14 PM Microsoft-Windows-FilterManager 6 None File System Filter 'luafv' (10.0, ‎1996‎-‎01‎-‎27T04:16:28.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:14 PM Microsoft-Windows-FilterManager 6 None File System Filter 'wcifs' (10.0, ‎2043‎-‎11‎-‎04T03:04:53.000000000Z) has successfully loaded and registered with Filter Manager. Warning 12/5/2025 10:01:14 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Warning 12/5/2025 10:01:14 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Information 12/5/2025 10:01:13 PM Microsoft-Windows-Directory-Services-SAM 16983 None "The security account manager is now logging periodic summary events for remote clients that call legacy password change or set RPC methods. For more information please see https://go.microsoft.com/fwlink/?linkid=2150956. " Information 12/5/2025 10:01:13 PM Microsoft-Windows-Directory-Services-SAM 16977 None "The domain is configured with the following minimum password length-related settings. MinimumPasswordLength: 0 RelaxMinimumPasswordLengthLimits: 0 MinimumPasswordLengthAudit: -1 For more information see https://go.microsoft.com/fwlink/?LinkId=2097191. " Information 12/5/2025 10:01:13 PM Microsoft-Windows-Directory-Services-SAM 16962 None "Remote calls to the SAM database are being restricted using the default security descriptor: O:SYG:SYD:(A;;RC;;;BA). For more information please see http://go.microsoft.com/fwlink/?LinkId=787651." Information 12/5/2025 10:01:13 PM Microsoft-Windows-Wininit 14 None Credential Guard configuration: 0x0, 0 Warning 12/5/2025 10:01:12 PM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 12/5/2025 10:01:12 PM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Information 12/5/2025 10:01:11 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 12/5/2025 10:01:08 PM NETwNe64 7036 None The \Device\NDMP4 service entered the Intel(R) Centrino(R) Wireless-N 2230 #2 state. Information 12/5/2025 10:01:08 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 3 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 12/5/2025 10:01:08 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 1 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 12/5/2025 10:01:08 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 2 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 12/5/2025 10:01:08 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 0 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 12/5/2025 10:01:08 PM Microsoft-Windows-Ntfs 98 None Volume \\?\Volume{df4bd8a4-f614-4d33-bbb6-6885459a0935} (\Device\HarddiskVolume1) is healthy. No action is needed. Information 12/5/2025 10:01:07 PM Microsoft-Windows-Ntfs 98 None Volume D: (\Device\HarddiskVolume5) is healthy. No action is needed. Information 12/5/2025 10:01:07 PM Microsoft-Windows-Kernel-Power 172 (203) Connectivity state in standby: Disconnected, Reason: NIC compliance Critical 12/5/2025 10:01:07 PM 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. Information 12/5/2025 10:01:07 PM Microsoft-Windows-FilterManager 6 None File System Filter 'npsvctrig' (10.0, ‎2025‎-‎01‎-‎05T18:41:12.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'UCPD' (10.0, ‎2006‎-‎08‎-‎28T03:56:22.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileCrypt' (10.0, ‎2002‎-‎03‎-‎01T03:12:42.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-Ntfs 98 None Volume C: (\Device\HarddiskVolume4) is healthy. No action is needed. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'WdFilter' (10.0, ‎2029‎-‎01‎-‎09T21:59:29.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'Wof' (10.0, ‎2090‎-‎03‎-‎16T10:56:17.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (10.0, ‎2062‎-‎12‎-‎22T21:21:06.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:05 PM Microsoft-Windows-HAL 16 None The iommu fault reporting has been initialized. Information 12/5/2025 10:01:14 PM EventLog 6013 None The system uptime is 9 seconds. Information 12/5/2025 10:01:14 PM EventLog 6005 None The Event log service was started. Information 12/5/2025 10:01:14 PM EventLog 6009 None Microsoft (R) Windows (R) 10.00. 19045 Multiprocessor Free. Error 12/5/2025 10:01:14 PM EventLog 6008 None The previous system shutdown at 10:01:06 PM on ‎12/‎5/‎2025 was unexpected. Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-General 20 (6) "The leap second configuration has been updated. Reason: Leap second data initialized from registry during boot Leap seconds enabled: true New leap second count: 0 Old leap second count: 0" Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-Boot 30 (21) The firmware reported boot metrics. Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-Boot 32 (58) The bootmgr spent 0 ms waiting for user input. Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-Boot 18 (57) There are 0x1 boot options on this system. Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-Boot 27 (33) The boot type was 0x0. Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-Boot 25 (32) The boot menu policy was 0x1. Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-Boot 238 (101) EFI time zone bias: 2047. Daylight flags: 0 Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-Boot 20 (31) The last shutdown's success status was false. The last boot's success status was true. Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-Boot 153 (62) Virtualization-based security (policies: 0) is disabled. Information 12/5/2025 10:01:05 PM Microsoft-Windows-Kernel-General 12 (1) The operating system started at system time ‎2025‎-‎12‎-‎06T06:01:04.937385000Z. Error 12/12/2025 11:52:06 PM Microsoft-Windows-DistributedCOM 10029 None The activation of the CLSID Windows.Internal.CapabilityAccess.CapabilityAccess timed out waiting for the service camsvc to stop. Error 12/12/2025 11:15:40 PM Microsoft-Windows-DistributedCOM 10029 None The activation of the CLSID Windows.Internal.CapabilityAccess.CapabilityAccess timed out waiting for the service camsvc to stop. Error 12/12/2025 10:23:46 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/12/2025 10:20:55 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Information 12/12/2025 10:20:37 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\73bd0ed29922a11_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Error 12/12/2025 10:10:46 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 10:10:46 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Warning 12/12/2025 10:02:03 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/12/2025 10:02:03 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/12/2025 10:02:03 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/12/2025 10:02:03 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 12/12/2025 9:59:09 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 9:47:58 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 9:47:57 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/12/2025 6:06:02 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.YourPhone_1.25072.79.0_x64__8wekyb3d8bbwe!App.AppXn958k7nsj8mxxmsepqdam8xk948t30sc.mca did not register with DCOM within the required timeout. Error 12/12/2025 6:01:20 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 6:01:19 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/12/2025 6:00:40 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 6:00:39 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/12/2025 5:57:16 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 5:57:16 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 12/12/2025 5:53:53 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/12/2025 5:48:55 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Information 12/12/2025 5:35:55 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 12/12/2025 5:30:27 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Wallet_2.4.18324.0_x64__8wekyb3d8bbwe!App.AppXgvxkrr1tm1jwgecmqbxe81yfbwpjdn1h.mca did not register with DCOM within the required timeout. Error 12/12/2025 5:30:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 5:28:58 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 5:18:37 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 5:16:32 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 12/12/2025 5:16:31 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 5:16:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 12/12/2025 5:16:27 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 5:15:08 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 12/12/2025 5:15:07 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 5:15:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 12/12/2025 5:10:13 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 5:03:19 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 12/12/2025 5:03:18 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 5:03:16 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 12/12/2025 4:54:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 4:49:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/12/2025 4:49:05 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 4:47:46 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 4:47:43 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 12/12/2025 4:47:36 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 4:47:34 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 12/12/2025 4:39:22 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 4:33:05 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 12/12/2025 4:33:05 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 4:33:03 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Information 12/12/2025 3:56:38 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 12/12/2025 3:56:33 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 3:47:45 PM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Information 12/12/2025 3:46:22 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 12/12/2025 3:44:00 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 3:44:00 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/12/2025 3:43:06 PM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.IrisService.AppX9vt1fs6dqgjpa4d1gsrdvr2kg9rrqk5d.mca did not register with DCOM within the required timeout. Error 12/12/2025 3:37:42 PM Microsoft-Windows-DistributedCOM 10029 None The activation of the CLSID Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager timed out waiting for the service camsvc to stop. Error 12/12/2025 3:13:10 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 3:10:46 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.4239_neutral_neutral_cw5n1h2txyewy!Windows.Networking.BackgroundTransfer.Internal.NetworkChangeTask.ClassId.1 did not register with DCOM within the required timeout. Error 12/12/2025 3:09:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/12/2025 3:06:50 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 3:06:15 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 3:00:40 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/12/2025 3:00:28 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 2:59:34 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 12/12/2025 2:59:32 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 2:59:30 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 12/12/2025 2:50:34 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 2:50:05 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 12/12/2025 2:50:03 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 2:50:03 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 2:50:01 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/12/2025 2:50:01 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/12/2025 2:50:01 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 12/12/2025 2:40:20 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 12/12/2025 2:40:20 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 2:40:19 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/12/2025 2:40:19 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 12/12/2025 2:16:44 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 1:14:28 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 12:55:29 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 12:51:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/12/2025 12:40:04 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 12:39:08 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 12:39:07 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/12/2025 12:38:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 12:37:52 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 12/12/2025 12:37:49 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 12:37:49 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 12:37:47 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 12/12/2025 12:37:47 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Information 12/12/2025 12:00:03 PM EventLog 6013 None The system uptime is 568741 seconds. Error 12/12/2025 11:51:37 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 11:51:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/12/2025 11:27:49 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 11:21:37 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 11:07:00 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 11:03:44 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/12/2025 10:50:33 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 10:47:47 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 10:41:07 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 10:39:26 AM Service Control Manager 7000 None "The Microsoft Defender Antivirus Network Inspection Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 10:39:25 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Defender Antivirus Network Inspection Service service to connect. Error 12/12/2025 10:33:45 AM Service Control Manager 7034 None The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 3 time(s). Error 12/12/2025 10:33:24 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 10:29:57 AM Service Control Manager 7031 None The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Error 12/12/2025 10:27:08 AM Service Control Manager 7031 None The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Error 12/12/2025 10:26:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 10:16:28 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/12/2025 10:12:13 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 10:12:13 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/12/2025 9:32:09 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXf8r3d8cn5hd71h9jyzah6ak9f3shj2d2.mca did not register with DCOM within the required timeout. Error 12/12/2025 9:18:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/12/2025 8:41:31 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/12/2025 8:28:09 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 8:28:09 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Information 12/12/2025 7:02:36 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 12/12/2025 7:02:36 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 12/12/2025 6:31:39 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 6:31:39 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/12/2025 6:30:55 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 6:30:54 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/12/2025 6:29:00 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 6:29:00 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/12/2025 6:08:42 AM Microsoft-Windows-DistributedCOM 10029 None The activation of the CLSID Windows.Internal.CapabilityAccess.CapabilityAccess timed out waiting for the service camsvc to stop. Error 12/12/2025 5:56:46 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXf8r3d8cn5hd71h9jyzah6ak9f3shj2d2.mca did not register with DCOM within the required timeout. Error 12/12/2025 5:49:16 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/12/2025 5:35:56 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 5:35:56 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/12/2025 5:27:28 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 5:23:32 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 5:23:31 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/12/2025 4:45:24 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/12/2025 4:15:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/12/2025 3:26:37 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.Accounts.AppXczw5m0gs1v24mkf1zqkkpebvayhcn73d.mca did not register with DCOM within the required timeout. Error 12/12/2025 3:26:37 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.RulesEngine.AppX5z5kfs8055rf6ttb3wq8ztd1bbgncvdy.mca did not register with DCOM within the required timeout. Error 12/12/2025 3:18:45 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 3:18:45 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Information 12/12/2025 3:15:46 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 12/12/2025 3:09:06 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Information 12/12/2025 3:07:38 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 12/12/2025 3:05:53 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 12/12/2025 3:05:52 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 3:05:51 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 12/12/2025 3:05:51 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 3:05:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/12/2025 3:03:02 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 3:03:01 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/12/2025 3:03:01 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/12/2025 2:58:49 AM Microsoft-Windows-DistributedCOM 10029 None The activation of the CLSID {659CDEA7-489E-11D9-A9CD-000D56965251} timed out waiting for the service BITS to stop. Error 12/12/2025 2:53:21 AM Microsoft-Windows-DistributedCOM 10029 None The activation of the CLSID {659CDEA7-489E-11D9-A9CD-000D56965251} timed out waiting for the service BITS to stop. Error 12/12/2025 2:47:14 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 12/12/2025 2:46:33 AM Service Control Manager 7024 None "The Background Intelligent Transfer Service service terminated with the following service-specific error: Call was canceled by the message filter." Error 12/12/2025 2:46:32 AM Microsoft-Windows-Bits-Client 16392 None The BITS service failed to start. Error 0x80010002. Error 12/12/2025 2:45:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 12/12/2025 2:16:01 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 2:16:01 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/12/2025 2:09:08 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 2:09:08 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/12/2025 1:38:06 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXf8r3d8cn5hd71h9jyzah6ak9f3shj2d2.mca did not register with DCOM within the required timeout. Error 12/12/2025 1:32:56 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/12/2025 1:32:55 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Information 12/11/2025 11:41:36 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/11/2025 11:00:53 PM Service Control Manager 7031 None The Connected User Experiences and Telemetry service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. Error 12/11/2025 10:43:26 PM Service Control Manager 7031 None The Microsoft Defender Antivirus Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service. Error 12/11/2025 10:38:04 PM Service Control Manager 7031 None The Geolocation Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. Error 12/11/2025 10:38:03 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 10:38:02 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 10:18:47 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 10:18:46 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 10:07:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 10:07:30 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 10:06:08 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 10:06:06 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Warning 12/11/2025 10:02:05 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/11/2025 10:02:05 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/11/2025 10:02:05 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/11/2025 10:02:05 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 12/11/2025 9:57:22 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 9:54:39 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 9:43:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 9:42:02 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 9:42:01 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 9:30:15 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 9:27:55 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 9:24:23 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 9:21:19 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 9:21:19 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 9:01:27 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 8:59:38 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 8:54:19 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 8:52:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 8:51:08 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/11/2025 8:47:45 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 8:47:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 8:43:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 8:43:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 8:34:46 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/11/2025 8:28:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 8:27:34 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 8:23:06 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 8:21:34 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 8:21:34 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 8:21:12 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 12/11/2025 8:20:35 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 12/11/2025 8:15:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 8:09:15 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 8:01:39 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 7:55:10 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 7:47:36 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 7:33:45 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 7:32:34 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 7:30:20 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 7:29:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 7:25:51 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 7:25:51 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 7:22:54 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 7:21:09 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 7:19:24 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 7:19:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 7:17:41 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 7:17:32 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 7:17:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 7:16:49 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 7:09:02 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 7:02:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 7:01:28 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 7:01:13 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 6:49:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 6:46:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 6:43:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/11/2025 6:40:26 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 6:38:29 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 6:37:20 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 6:35:39 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 6:30:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 6:30:35 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 6:27:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 6:27:07 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/11/2025 6:26:57 PM Service Control Manager 7000 None "The Windows Push Notifications System Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 6:26:55 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Push Notifications System Service service to connect. Error 12/11/2025 6:26:46 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.YourPhone_1.25072.79.0_x64__8wekyb3d8bbwe!App.AppXn958k7nsj8mxxmsepqdam8xk948t30sc.mca did not register with DCOM within the required timeout. Error 12/11/2025 6:25:27 PM Service Control Manager 7031 None The Windows Push Notifications System Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service. Error 12/11/2025 6:25:25 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 6:22:31 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 6:19:37 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 6:16:03 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 6:16:03 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 6:14:56 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 6:14:56 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/11/2025 6:13:39 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 6:13:37 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 6:12:55 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 6:12:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/11/2025 6:02:30 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:59:16 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:57:55 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:56:08 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:54:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:53:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:53:06 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 5:49:59 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 5:47:30 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:46:49 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:46:18 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:45:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 5:43:57 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:41:35 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 5:38:20 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:38:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 5:37:11 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:37:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:35:18 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:30:13 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/11/2025 5:30:05 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:27:15 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:25:43 PM Service Control Manager 7000 None "The Microsoft Passport service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 5:25:40 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Passport service to connect. Error 12/11/2025 5:25:36 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:25:09 PM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.IrisService.AppX9vt1fs6dqgjpa4d1gsrdvr2kg9rrqk5d.mca did not register with DCOM within the required timeout. Error 12/11/2025 5:23:43 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 5:22:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:20:20 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:15:03 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 5:15:02 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 5:13:59 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:02:28 PM Microsoft-Windows-DistributedCOM 10010 None The server {73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} did not register with DCOM within the required timeout. Error 12/11/2025 5:02:28 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 4:57:46 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 4:57:03 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 4:54:24 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 4:53:45 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 4:51:45 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 4:47:16 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 4:47:05 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 4:46:18 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 4:40:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 4:40:21 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 4:38:44 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 4:38:04 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 4:35:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 4:35:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/11/2025 4:34:19 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 4:34:06 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/11/2025 4:34:07 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 4:32:38 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 4:25:36 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 4:23:59 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 4:20:22 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Wallet_2.4.18324.0_x64__8wekyb3d8bbwe!App.AppXgvxkrr1tm1jwgecmqbxe81yfbwpjdn1h.mca did not register with DCOM within the required timeout. Error 12/11/2025 4:19:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 4:19:07 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.4239_neutral_neutral_cw5n1h2txyewy!Windows.Networking.BackgroundTransfer.Internal.NetworkChangeTask.ClassId.1 did not register with DCOM within the required timeout. Error 12/11/2025 4:17:52 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 4:06:42 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 4:03:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:56:15 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:49:46 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:44:08 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 12/11/2025 3:44:06 PM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 3:44:03 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 12/11/2025 3:44:02 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 3:43:14 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:36:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:32:28 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 12/11/2025 3:32:26 PM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 3:32:24 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 12/11/2025 3:32:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 3:30:15 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:22:53 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:16:04 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:16:04 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/11/2025 3:13:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:10:36 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 3:10:35 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 3:06:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 3:00:21 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 2:53:43 PM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 12/11/2025 2:42:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 12/11/2025 2:35:27 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/11/2025 2:34:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/11/2025 2:31:54 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 2:28:43 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 2:28:25 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 2:28:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 2:28:21 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 2:26:42 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 2:26:39 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 2:22:06 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 2:15:31 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 2:10:15 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 2:10:15 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 2:08:58 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 2:01:11 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXf8r3d8cn5hd71h9jyzah6ak9f3shj2d2.mca did not register with DCOM within the required timeout. Error 12/11/2025 1:12:25 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 1:12:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 1:09:40 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 1:09:39 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Information 12/11/2025 12:00:01 PM EventLog 6013 None The system uptime is 482338 seconds. Information 12/11/2025 11:59:58 AM EventLog 6013 None The system uptime is 482336 seconds. Error 12/11/2025 11:33:49 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/11/2025 11:11:28 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 11:11:27 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 10:48:07 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 10:19:47 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 10:19:45 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 10:11:36 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 10:11:34 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 10:10:20 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 10:10:20 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 10:09:37 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/11/2025 9:30:06 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 9:30:06 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 9:18:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 9:06:23 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/11/2025 9:00:07 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 8:38:17 AM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 12/11/2025 8:31:43 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 8:29:20 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 8:10:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/11/2025 7:28:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 6:19:41 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 6:00:22 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/11/2025 5:50:24 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:47:15 AM Microsoft-Windows-DistributedCOM 10029 None The activation of the CLSID Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager timed out waiting for the service camsvc to stop. Error 12/11/2025 5:27:31 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 5:26:56 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 5:25:33 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 4:11:02 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 4:09:07 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 4:09:07 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/11/2025 3:58:26 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.Accounts.AppXczw5m0gs1v24mkf1zqkkpebvayhcn73d.mca did not register with DCOM within the required timeout. Error 12/11/2025 3:58:26 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.RulesEngine.AppX5z5kfs8055rf6ttb3wq8ztd1bbgncvdy.mca did not register with DCOM within the required timeout. Error 12/11/2025 3:54:30 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 3:20:26 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 3:20:26 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/11/2025 3:13:55 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 3:13:55 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/11/2025 2:50:06 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.CrossDevice_0.25072.59.0_x64__cw5n1h2txyewy!SettingsUXHostApp.AppXxnb2wgd17pheptmaxx5ykxp7bcmqe4ra.mca did not register with DCOM within the required timeout. Error 12/11/2025 2:46:07 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 2:46:07 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 12/11/2025 2:42:22 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 12/11/2025 2:38:21 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Information 12/11/2025 2:36:50 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 12/11/2025 2:13:21 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 2:13:21 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/11/2025 2:08:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 1:33:26 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 1:23:13 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 1:21:42 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service edgeupdate with arguments ""/comsvc"" in order to run the server: {CECDDD22-2E72-4832-9606-A9B0E5E344B2}" Error 12/11/2025 1:21:34 AM Service Control Manager 7000 None "The Microsoft Edge Update Service (edgeupdate) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/11/2025 1:21:33 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Edge Update Service (edgeupdate) service to connect. Error 12/11/2025 1:09:49 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 1:03:07 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 12:50:10 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 12:49:44 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 12:45:56 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 12:45:04 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 12:42:04 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 12:30:29 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 12/11/2025 12:24:20 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 12:23:44 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/11/2025 12:22:32 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 12:16:32 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 12:12:02 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/11/2025 12:12:01 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/11/2025 12:09:51 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service LxpSvc with arguments ""Unavailable"" in order to run the server: {D0582E3B-3126-4CAA-9155-AC37C912A489}" Error 12/11/2025 12:09:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Language Experience Service service to connect. Error 12/11/2025 12:04:58 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/10/2025 11:53:10 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/10/2025 11:52:39 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/10/2025 11:46:10 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/10/2025 11:46:02 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/10/2025 11:36:29 PM Service Control Manager 7000 None "The Microsoft Defender Antivirus Network Inspection Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 11:36:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Defender Antivirus Network Inspection Service service to connect. Error 12/10/2025 11:26:59 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/10/2025 11:24:22 PM Service Control Manager 7031 None The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Error 12/10/2025 11:20:37 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/10/2025 11:19:59 PM Service Control Manager 7031 None The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Error 12/10/2025 11:09:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/10/2025 10:58:51 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 10:58:50 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/10/2025 10:42:08 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/10/2025 10:11:59 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Warning 12/10/2025 10:02:07 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 12/10/2025 10:02:07 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 12/10/2025 10:02:07 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 12/10/2025 10:02:07 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Error 12/10/2025 9:59:06 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Information 12/10/2025 8:23:07 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/10/2025 8:00:24 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/10/2025 7:41:45 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 7:41:45 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 12/10/2025 6:23:26 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 6:23:26 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/10/2025 6:18:55 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/10/2025 6:17:29 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 6:17:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/10/2025 5:51:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/10/2025 4:59:43 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/10/2025 4:43:43 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Information 12/10/2025 3:26:11 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/10/2025 3:21:40 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 12/10/2025 2:51:49 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.4239_neutral_neutral_cw5n1h2txyewy!Windows.Networking.BackgroundTransfer.Internal.NetworkChangeTask.ClassId.1 did not register with DCOM within the required timeout. Error 12/10/2025 2:36:59 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Information 12/10/2025 1:02:53 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 5 keys and creating 1 modified pages. Error 12/10/2025 12:51:42 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.XboxGamingOverlay_7.325.11061.0_x64__8wekyb3d8bbwe!App.AppXrfdt3p0f38tc4nxz7ajrd5as6ctb0dck.mca did not register with DCOM within the required timeout. Error 12/10/2025 12:47:06 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 12:47:06 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Information 12/10/2025 12:00:00 PM EventLog 6013 None The system uptime is 395938 seconds. Information 12/10/2025 11:59:58 AM EventLog 6013 None The system uptime is 395936 seconds. Information 12/10/2025 11:16:57 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/10/2025 9:29:42 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/10/2025 9:15:54 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/10/2025 8:41:17 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 8:41:17 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/10/2025 8:40:29 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 8:40:29 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/10/2025 5:58:00 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 5:58:00 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/10/2025 5:57:00 AM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Error 12/10/2025 5:38:17 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/10/2025 5:36:20 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 12/10/2025 3:00:20 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/10/2025 3:00:20 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 12/10/2025 2:37:26 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/10/2025 2:33:43 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 12/10/2025 12:29:56 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Warning 12/9/2025 10:02:09 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/9/2025 10:02:09 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/9/2025 10:02:09 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/9/2025 10:02:09 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 12/9/2025 5:54:12 PM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Error 12/9/2025 5:47:07 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/9/2025 5:47:07 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 12/9/2025 5:04:40 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/9/2025 3:22:58 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/9/2025 3:20:29 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/9/2025 12:00:00 PM EventLog 6013 None The system uptime is 309538 seconds. Information 12/9/2025 11:59:58 AM EventLog 6013 None The system uptime is 309536 seconds. Information 12/9/2025 6:53:28 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 12/9/2025 6:53:28 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 12/9/2025 5:53:45 AM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Warning 12/9/2025 2:42:02 AM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 12/9/2025 2:34:19 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/9/2025 2:29:55 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/9/2025 2:18:13 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/9/2025 2:12:57 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/9/2025 2:05:54 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/9/2025 2:03:23 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 12/8/2025 11:24:11 PM Microsoft-Windows-WindowsUpdateClient 20 Windows Update Agent Installation Failure: Windows failed to install the following update with error 0x8024200B: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.814.0) - Current Channel (Broad). Information 12/8/2025 11:21:43 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.814.0) - Current Channel (Broad) Error 12/8/2025 11:21:25 PM Microsoft-Windows-WindowsUpdateClient 20 Windows Update Agent Installation Failure: Windows failed to install the following update with error 0x80242007: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.814.0) - Current Channel (Broad). Information 12/8/2025 10:52:24 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Warning 12/8/2025 10:02:10 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/8/2025 10:02:10 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/8/2025 10:02:10 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/8/2025 10:02:10 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Information 12/8/2025 8:46:56 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.Search_cw5n1h2txyewy\Settings\settings.dat was cleared updating 36 keys and creating 7 modified pages. Information 12/8/2025 5:32:58 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\microsoft.windows.search_cw5n1h2txyewy\AC\GEH\POF.dat was cleared updating 6 keys and creating 1 modified pages. Information 12/8/2025 3:21:14 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/8/2025 3:18:48 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/8/2025 1:46:15 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/8/2025 12:00:00 PM EventLog 6013 None The system uptime is 223138 seconds. Information 12/8/2025 11:59:58 AM EventLog 6013 None The system uptime is 223136 seconds. Information 12/8/2025 7:21:08 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.814.0) - Current Channel (Broad) Information 12/8/2025 7:21:08 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/8/2025 4:40:07 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/8/2025 1:45:49 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/8/2025 1:43:42 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/8/2025 1:16:50 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 12/8/2025 12:16:16 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/8/2025 12:13:56 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Warning 12/8/2025 12:01:12 AM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 12/7/2025 10:13:48 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.805.0) - Current Channel (Broad) Information 12/7/2025 10:12:30 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.805.0) - Current Channel (Broad) Information 12/7/2025 10:12:30 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Warning 12/7/2025 10:02:12 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/7/2025 10:02:12 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/7/2025 10:02:12 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/7/2025 10:02:12 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Information 12/7/2025 7:33:58 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/7/2025 7:30:32 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\System32\config\COMPONENTS was cleared updating 85551 keys and creating 9901 modified pages. Information 12/7/2025 5:48:20 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/7/2025 5:46:10 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/7/2025 4:51:50 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\AD2F1837.HPPrinterControl_v10z8vjag6ke6\Settings\settings.dat was cleared updating 3 keys and creating 1 modified pages. Information 12/7/2025 3:20:25 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/7/2025 3:18:20 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/7/2025 12:08:08 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 13 keys and creating 3 modified pages. Information 12/7/2025 12:00:00 PM EventLog 6013 None The system uptime is 136738 seconds. Information 12/7/2025 11:59:58 AM EventLog 6013 None The system uptime is 136736 seconds. Information 12/7/2025 10:27:50 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/7/2025 10:14:06 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\Settings\settings.dat was cleared updating 12348 keys and creating 373 modified pages. Information 12/7/2025 8:43:30 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.794.0) - Current Channel (Broad) Information 12/7/2025 8:42:55 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.794.0) - Current Channel (Broad) Information 12/7/2025 8:42:55 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/7/2025 4:05:50 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Settings\settings.dat was cleared updating 5 keys and creating 1 modified pages. Information 12/7/2025 1:45:44 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/7/2025 1:43:38 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/7/2025 1:21:42 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/7/2025 1:13:20 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/7/2025 1:11:07 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/7/2025 12:57:08 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/7/2025 12:55:02 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/6/2025 10:12:21 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.782.0) - Current Channel (Broad) Information 12/6/2025 10:11:57 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.782.0) - Current Channel (Broad) Information 12/6/2025 10:11:57 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Warning 12/6/2025 10:02:14 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Warning 12/6/2025 10:02:14 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Warning 12/6/2025 10:02:14 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Warning 12/6/2025 10:02:14 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Information 12/6/2025 5:46:09 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.YourPhone_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\d4be7e4a3deb5b23_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Information 12/6/2025 5:46:09 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.YourPhone_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 46 keys and creating 5 modified pages. Information 12/6/2025 4:15:34 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/6/2025 3:20:20 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/6/2025 3:18:13 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/6/2025 1:50:43 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.773.0) - Current Channel (Broad) Information 12/6/2025 1:50:19 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.773.0) - Current Channel (Broad) Information 12/6/2025 1:50:19 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/6/2025 12:00:00 PM EventLog 6013 None The system uptime is 50338 seconds. Information 12/6/2025 11:59:59 AM EventLog 6013 None The system uptime is 50337 seconds. Information 12/6/2025 7:09:26 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/6/2025 1:45:45 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/6/2025 1:43:39 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/6/2025 12:57:02 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/6/2025 12:54:50 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/6/2025 12:05:05 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/6/2025 12:03:00 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/5/2025 11:11:52 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 12/5/2025 10:54:48 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 12/5/2025 10:37:44 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 12/5/2025 10:20:40 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 12/5/2025 10:20:39 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRD29V9-MICROSOFT.MICROSOFTOFFICEHUB Information 12/5/2025 10:20:37 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRD29V9-MICROSOFT.MICROSOFTOFFICEHUB Information 12/5/2025 10:20:37 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9NHT9RB2F4HD-Microsoft.Copilot Information 12/5/2025 10:20:36 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Copilot_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 12/5/2025 10:20:35 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9NHT9RB2F4HD-Microsoft.Copilot Information 12/5/2025 10:20:35 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9NKRJ3SJ9SDG-Microsoft.WindowsAppRuntime.1.8 Information 12/5/2025 10:20:31 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.MicrosoftOfficeHub_19.2512.33091.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 12/5/2025 10:19:33 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9NKRJ3SJ9SDG-Microsoft.WindowsAppRuntime.1.8 Information 12/5/2025 10:19:26 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE Information 12/5/2025 10:19:14 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE Information 12/5/2025 10:19:09 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.WindowsStore_22510.1401.4.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 12/5/2025 10:19:01 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:18:54 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRFJ3PT-MICROSOFT.ZUNEMUSIC Information 12/5/2025 10:18:50 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.ZuneMusic_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 12/5/2025 10:18:49 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRFJ3PT-MICROSOFT.ZUNEMUSIC Information 12/5/2025 10:18:40 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.ZuneMusic_11.2510.7.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 12/5/2025 10:18:18 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:18:18 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:18:13 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:17:58 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRFJBBG-MICROSOFT.WINDOWSCAMERA Information 12/5/2025 10:17:56 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.WindowsCamera_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 12/5/2025 10:17:55 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRFJBBG-MICROSOFT.WINDOWSCAMERA Information 12/5/2025 10:17:48 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.WindowsCamera_2025.2510.2.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 12/5/2025 10:17:41 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:17:35 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9N4D0MSMP0PT-Microsoft.VP9VideoExtensions Information 12/5/2025 10:17:33 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.VP9VideoExtensions_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 12/5/2025 10:17:33 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9N4D0MSMP0PT-Microsoft.VP9VideoExtensions Information 12/5/2025 10:17:20 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/5/2025 10:17:16 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:17:16 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:17:16 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:15:16 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/5/2025 10:14:21 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.755.0) - Current Channel (Broad) Information 12/5/2025 10:13:40 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.755.0) - Current Channel (Broad) Information 12/5/2025 10:13:04 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-Provisioning-Sequence.dat was cleared updating 0 keys and creating 0 modified pages. Information 12/5/2025 10:12:06 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:12:06 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/5/2025 10:11:58 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Warning 12/5/2025 10:06:51 PM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Error 12/5/2025 10:06:07 PM Microsoft-Windows-TPM-WMI 1801 None "Secure Boot CA/keys need to be updated. This device signature information is included here. DeviceAttributes: BaseBoardManufacturer:INTEL Corporation;FirmwareManufacturer:American Megatrends Inc.;FirmwareVersion:5.6.5;OEMModelNumber:To be filled by O.E.M.;OEMModelBaseBoard:CRESCENTBAY;OEMModelSystemFamily:To be filled by O.E.M.;OEMManufacturerName:To be filled by O.E.M.;OEMModelSKU:To be filled by O.E.M.;OSArchitecture:amd64; BucketId: 3172bfdf51002a90ec09ce6a4c3dd16df4a8a200aa84b1d0136a4916f76764e2 BucketConfidenceLevel: UpdateType: 0 HResult: The operation completed successfully." Information 12/5/2025 10:03:36 PM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎12‎-‎06T06:03:36.284054500Z from ‎2025‎-‎12‎-‎06T06:03:36.283104100Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 9816)." Information 12/5/2025 10:03:36 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 12/5/2025 10:03:36 PM Microsoft-Windows-Time-Service 35 None The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123) with reference id 494637363. Current local stratum number is 4. Information 12/5/2025 10:03:36 PM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎12‎-‎06T06:03:36.283104100Z from ‎2025‎-‎12‎-‎06T06:03:32.787211100Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 9816)." Information 12/5/2025 10:03:36 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 12/5/2025 10:03:18 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Warning 12/5/2025 10:03:16 PM 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." Warning 12/5/2025 10:03:16 PM 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.WscBrokerManager 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." Warning 12/5/2025 10:03:16 PM 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.SecurityAppBroker 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." Information 12/5/2025 10:03:16 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Warning 12/5/2025 10:02:12 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 12/5/2025 10:02:12 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 12/5/2025 10:02:12 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 12/5/2025 10:02:12 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Information 12/5/2025 10:02:11 PM Microsoft-Windows-WER-SystemErrorReporting 1018 None The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space. Error 12/5/2025 10:02:03 PM Microsoft-Windows-WER-SystemErrorReporting 1001 None The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x000000000000003f, 0x00000000000b46da, 0x0000000071d3b1d3, 0x00000000b8471d6a). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 51349f6c-9363-4ba5-83ed-b79cee66a8f8. Error 12/5/2025 10:01:35 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/5/2025 10:01:35 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/5/2025 10:01:35 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/5/2025 10:01:35 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/5/2025 10:01:35 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/5/2025 10:01:35 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/5/2025 10:01:35 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/5/2025 10:01:35 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Warning 12/5/2025 10:01:18 PM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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 12/5/2025 10:01:18 PM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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." Information 12/5/2025 10:01:15 PM Service Control Manager 7026 None "The following boot-start or system-start driver(s) did not load: dam" Information 12/5/2025 10:01:13 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\config\DRIVERS was cleared updating 746 keys and creating 90 modified pages. Error 12/5/2025 10:01:10 PM Service Control Manager 7034 None The MediaMTX service terminated unexpectedly. It has done this 1 time(s). Error 12/5/2025 10:01:10 PM Service Control Manager 7024 None "The MediaMTX service terminated with the following service-specific error: The system cannot find the path specified." Information 12/5/2025 10:01:10 PM Microsoft-Windows-Winlogon 7001 (1101) User Logon Notification for Customer Experience Improvement Program Information 12/5/2025 10:01:09 PM Microsoft-Windows-WLAN-AutoConfig 4000 None "WLAN AutoConfig service has successfully started. " Information 12/5/2025 10:01:07 PM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection #2 Network link has been established at 1Gbps full duplex. " Information 12/5/2025 10:01:07 PM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection Network link has been established at 1Gbps full duplex. " Information 12/5/2025 10:01:06 PM Microsoft-Windows-DHCPv6-Client 51046 Service State Event DHCPv6 client service is started Information 12/5/2025 10:01:06 PM Microsoft-Windows-Dhcp-Client 50103 Service State Event DHCPv4 client registered for shutdown notification Information 12/5/2025 10:01:06 PM Microsoft-Windows-Dhcp-Client 50036 Service State Event DHCPv4 client service is started Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'bindflt' (10.0, ‎2091‎-‎04‎-‎15T15:55:03.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'storqosflt' (10.0, ‎2038‎-‎12‎-‎03T01:18:20.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 1 None File System Filter 'CldFlt' (Version 10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) unloaded successfully. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'luafv' (10.0, ‎1996‎-‎01‎-‎27T04:16:28.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:06 PM Microsoft-Windows-FilterManager 6 None File System Filter 'wcifs' (10.0, ‎2043‎-‎11‎-‎04T03:04:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:05 PM Microsoft-Windows-Directory-Services-SAM 16983 None "The security account manager is now logging periodic summary events for remote clients that call legacy password change or set RPC methods. For more information please see https://go.microsoft.com/fwlink/?linkid=2150956. " Information 12/5/2025 10:01:05 PM Microsoft-Windows-Directory-Services-SAM 16977 None "The domain is configured with the following minimum password length-related settings. MinimumPasswordLength: 0 RelaxMinimumPasswordLengthLimits: 0 MinimumPasswordLengthAudit: -1 For more information see https://go.microsoft.com/fwlink/?LinkId=2097191. " Information 12/5/2025 10:01:05 PM Microsoft-Windows-Directory-Services-SAM 16962 None "Remote calls to the SAM database are being restricted using the default security descriptor: O:SYG:SYD:(A;;RC;;;BA). For more information please see http://go.microsoft.com/fwlink/?LinkId=787651." Information 12/5/2025 10:01:05 PM Microsoft-Windows-Wininit 14 None Credential Guard configuration: 0x0, 0 Warning 12/5/2025 10:01:05 PM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 12/5/2025 10:01:04 PM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Information 12/5/2025 10:01:04 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Warning 12/5/2025 10:01:03 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Warning 12/5/2025 10:01:03 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Information 12/5/2025 10:01:01 PM NETwNe64 7036 None The \Device\NDMP4 service entered the Intel(R) Centrino(R) Wireless-N 2230 #2 state. Information 12/5/2025 10:01:01 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 3 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 12/5/2025 10:01:01 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 1 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 12/5/2025 10:01:01 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 2 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 12/5/2025 10:01:01 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 0 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 12/5/2025 10:01:01 PM Microsoft-Windows-Ntfs 98 None Volume \\?\Volume{df4bd8a4-f614-4d33-bbb6-6885459a0935} (\Device\HarddiskVolume1) is healthy. No action is needed. Information 12/5/2025 10:01:01 PM Microsoft-Windows-Ntfs 98 None Volume D: (\Device\HarddiskVolume5) is healthy. No action is needed. Information 12/5/2025 10:01:00 PM Microsoft-Windows-Kernel-Power 172 (203) Connectivity state in standby: Disconnected, Reason: NIC compliance Critical 12/5/2025 10:01:00 PM 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. Information 12/5/2025 10:01:00 PM Microsoft-Windows-FilterManager 6 None File System Filter 'npsvctrig' (10.0, ‎2025‎-‎01‎-‎05T18:41:12.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:00 PM Microsoft-Windows-FilterManager 6 None File System Filter 'UCPD' (10.0, ‎2006‎-‎08‎-‎28T03:56:22.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:01:00 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileCrypt' (10.0, ‎2002‎-‎03‎-‎01T03:12:42.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:00:59 PM Microsoft-Windows-Ntfs 98 None Volume C: (\Device\HarddiskVolume4) is healthy. No action is needed. Information 12/5/2025 10:00:59 PM Microsoft-Windows-FilterManager 6 None File System Filter 'WdFilter' (10.0, ‎2029‎-‎01‎-‎09T21:59:29.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:00:59 PM Microsoft-Windows-FilterManager 6 None File System Filter 'Wof' (10.0, ‎2090‎-‎03‎-‎16T10:56:17.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:00:59 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (10.0, ‎2062‎-‎12‎-‎22T21:21:06.000000000Z) has successfully loaded and registered with Filter Manager. Information 12/5/2025 10:00:59 PM Microsoft-Windows-HAL 16 None The iommu fault reporting has been initialized. Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-General 20 (6) "The leap second configuration has been updated. Reason: Leap second data initialized from registry during boot Leap seconds enabled: true New leap second count: 0 Old leap second count: 0" Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-Boot 30 (21) The firmware reported boot metrics. Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-Boot 32 (58) The bootmgr spent 0 ms waiting for user input. Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-Boot 18 (57) There are 0x1 boot options on this system. Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-Boot 27 (33) The boot type was 0x0. Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-Boot 25 (32) The boot menu policy was 0x1. Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-Boot 238 (101) EFI time zone bias: 2047. Daylight flags: 0 Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-Boot 20 (31) The last shutdown's success status was false. The last boot's success status was true. Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-Boot 153 (62) Virtualization-based security (policies: 0) is disabled. Information 12/5/2025 10:01:06 PM EventLog 6013 None The system uptime is 8 seconds. Information 12/5/2025 10:01:06 PM EventLog 6005 None The Event log service was started. Information 12/5/2025 10:01:06 PM EventLog 6009 None Microsoft (R) Windows (R) 10.00. 19045 Multiprocessor Free. Error 12/5/2025 10:01:06 PM EventLog 6008 None The previous system shutdown at 10:10:58 AM on ‎11/‎30/‎2025 was unexpected. Information 12/5/2025 10:00:58 PM Microsoft-Windows-Kernel-General 12 (1) The operating system started at system time ‎2025‎-‎12‎-‎06T06:00:58.500000000Z. Error 12/5/2025 9:59:09 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:59:08 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 9:56:24 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:56:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/5/2025 9:56:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/5/2025 9:49:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/5/2025 9:48:59 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/5/2025 9:48:36 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:48:35 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 9:47:21 PM Service Control Manager 7000 None "The Microsoft Defender Antivirus Network Inspection Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:47:20 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Defender Antivirus Network Inspection Service service to connect. Error 12/5/2025 9:45:08 PM Service Control Manager 7031 None The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Error 12/5/2025 9:45:08 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:44:54 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/5/2025 9:40:48 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/5/2025 9:39:35 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:39:35 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 9:37:37 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/5/2025 9:36:35 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/5/2025 9:34:46 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:34:45 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 9:27:43 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/5/2025 9:25:19 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/5/2025 9:24:23 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:24:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 9:19:22 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:19:21 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 9:17:51 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/5/2025 9:15:26 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/5/2025 8:28:27 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 8:28:26 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 7:52:45 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 12/5/2025 6:38:51 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/5/2025 5:45:51 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 5:45:48 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Information 12/5/2025 5:39:17 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/5/2025 5:21:27 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 5:21:27 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 5:18:39 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 5:18:38 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 4:17:11 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 4:17:08 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/5/2025 4:16:21 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 12/5/2025 4:14:12 PM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 12/5/2025 3:26:05 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 3:26:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/5/2025 3:25:16 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 3:25:15 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/5/2025 3:20:08 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/5/2025 3:14:57 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 12/5/2025 3:04:15 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 3:04:15 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 2:34:17 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 2:34:17 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 2:33:24 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 2:33:24 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 2:28:28 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 2:28:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 1:30:07 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 1:30:06 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/5/2025 12:45:36 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 12:45:34 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/5/2025 12:00:00 PM EventLog 6013 None The system uptime is 438538 seconds. Information 12/5/2025 11:59:58 AM EventLog 6013 None The system uptime is 438536 seconds. Warning 12/5/2025 10:12:16 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 12/5/2025 10:12:16 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 12/5/2025 10:12:16 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 12/5/2025 10:12:16 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Error 12/5/2025 9:00:52 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 9:00:52 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/5/2025 8:33:09 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/5/2025 8:28:28 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 8:28:28 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 5:09:23 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 5:09:22 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/5/2025 4:35:29 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 12/5/2025 4:00:36 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 4:00:36 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/5/2025 3:27:04 AM Service Control Manager 7000 None "The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 3:27:03 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. Error 12/5/2025 3:08:12 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 3:08:12 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/5/2025 2:57:23 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.CrossDevice_0.25072.59.0_x64__cw5n1h2txyewy!SettingsUXHostApp.AppXxnb2wgd17pheptmaxx5ykxp7bcmqe4ra.mca did not register with DCOM within the required timeout. Error 12/5/2025 2:52:59 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 2:52:59 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/5/2025 2:46:19 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 2:46:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 2:27:41 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 2:27:41 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 2:01:16 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 2:01:15 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/5/2025 1:51:23 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 1:51:22 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/5/2025 1:46:20 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 1:46:20 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/5/2025 1:23:28 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/5/2025 1:23:28 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 12/4/2025 11:27:00 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/4/2025 11:09:48 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 11:09:46 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/4/2025 9:34:47 PM Service Control Manager 7000 None "The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 9:34:47 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. Error 12/4/2025 6:04:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Error 12/4/2025 5:27:42 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 5:27:42 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/4/2025 3:16:07 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/4/2025 3:13:31 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 12/4/2025 3:08:03 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 3:08:03 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/4/2025 2:21:04 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 2:21:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/4/2025 2:20:50 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/4/2025 2:16:01 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 2:16:00 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/4/2025 12:00:01 PM EventLog 6013 None The system uptime is 352139 seconds. Warning 12/4/2025 10:12:18 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86407 seconds since the last report. Warning 12/4/2025 10:12:18 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86407 seconds since the last report. Warning 12/4/2025 10:12:18 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86407 seconds since the last report. Warning 12/4/2025 10:12:18 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86407 seconds since the last report. Error 12/4/2025 6:54:47 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 6:54:46 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/4/2025 6:19:31 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 12/4/2025 6:19:31 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 12/4/2025 6:19:31 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 12/4/2025 6:04:16 AM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Information 12/4/2025 5:14:42 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/4/2025 3:17:52 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 3:17:51 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 12/4/2025 2:30:49 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 2:29:49 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 12/4/2025 2:28:16 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/4/2025 2:28:16 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXf8r3d8cn5hd71h9jyzah6ak9f3shj2d2.mca did not register with DCOM within the required timeout. Error 12/4/2025 2:28:11 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!ShellFeedsUI.AppXfbff151h5bmghg166fvn34ccayg70vts.mca did not register with DCOM within the required timeout. Error 12/4/2025 2:28:02 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.StorePurchaseApp_22509.1401.1.0_x64__8wekyb3d8bbwe!App.AppXh68f74x901gdx01kwdh3szc5yp7bnmah.mca did not register with DCOM within the required timeout. Error 12/4/2025 2:15:44 AM Service Control Manager 7000 None "The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 2:09:57 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXf8r3d8cn5hd71h9jyzah6ak9f3shj2d2.mca did not register with DCOM within the required timeout. Error 12/4/2025 1:52:45 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. Error 12/4/2025 1:38:07 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 1:38:07 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/4/2025 1:29:04 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/4/2025 1:29:04 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/4/2025 1:29:04 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/4/2025 1:29:04 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/4/2025 1:29:04 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/4/2025 1:29:04 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/4/2025 1:29:04 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/4/2025 1:29:04 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 12/4/2025 1:26:28 AM Service Control Manager 7011 None A timeout (30000 milliseconds) was reached while waiting for a transaction response from the FDResPub service. Information 12/4/2025 1:25:53 AM Microsoft-Windows-Power-Troubleshooter 1 None "The system has returned from a low power state. Sleep Time: ‎2025‎-‎12‎-‎04T09:23:09.369830800Z Wake Time: ‎2025‎-‎12‎-‎04T09:25:26.811338400Z Wake Source: Power Button" Warning 12/4/2025 1:24:49 AM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 12/4/2025 1:24:45 AM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection #2 Network link has been established at 1Gbps full duplex. " Information 12/4/2025 1:24:45 AM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection Network link has been established at 1Gbps full duplex. " Information 12/4/2025 1:24:41 AM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Warning 12/4/2025 1:24:40 AM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Warning 12/4/2025 1:24:40 AM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Information 12/4/2025 1:24:40 AM Microsoft-Windows-Kernel-Power 131 (33) Firmware S3 times. ResumeCount: 1, FullResume: 168, AverageResume: 168 Information 12/4/2025 1:24:35 AM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎12‎-‎04T09:24:35.500000000Z from ‎2025‎-‎12‎-‎04T09:24:26.976124800Z. Change Reason: System time synchronized with the hardware clock. Process: '' (PID 4)." Information 12/4/2025 1:24:26 AM Microsoft-Windows-Kernel-Power 107 (102) The system has resumed from sleep. Information 12/4/2025 1:24:21 AM Microsoft-Windows-Kernel-Power 42 (64) "The system is entering sleep. Sleep Reason: Button or Lid" Information 12/4/2025 1:23:56 AM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎12‎-‎04T09:23:56.689768900Z from ‎2025‎-‎12‎-‎04T09:23:56.688493100Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 8860)." Information 12/4/2025 1:23:56 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Error 12/4/2025 1:19:35 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 1:19:35 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/4/2025 1:16:56 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.YourPhone_1.25072.79.0_x64__8wekyb3d8bbwe!App.AppXn958k7nsj8mxxmsepqdam8xk948t30sc.mca did not register with DCOM within the required timeout. Error 12/4/2025 1:14:30 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/4/2025 1:14:30 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 12/4/2025 1:11:00 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.StorePurchaseApp_22509.1401.1.0_x64__8wekyb3d8bbwe!App.AppXh68f74x901gdx01kwdh3szc5yp7bnmah.mca did not register with DCOM within the required timeout. Error 12/3/2025 11:36:27 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 12/3/2025 11:32:36 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/3/2025 11:32:36 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/3/2025 8:08:27 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 12/3/2025 4:40:46 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/3/2025 4:40:46 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/3/2025 3:15:14 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/3/2025 3:12:55 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/3/2025 2:23:15 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 27 keys and creating 3 modified pages. Information 12/3/2025 12:00:00 PM EventLog 6013 None The system uptime is 265738 seconds. Information 12/3/2025 11:59:58 AM EventLog 6013 None The system uptime is 265736 seconds. Information 12/3/2025 11:02:17 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/3/2025 11:02:12 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\790b7f9a2cf25097_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Warning 12/3/2025 10:12:11 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/3/2025 10:12:11 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/3/2025 10:12:11 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 12/3/2025 10:12:11 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 12/3/2025 8:21:00 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 12/3/2025 8:21:00 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 12/3/2025 1:56:09 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/2/2025 9:37:54 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 12/2/2025 9:37:54 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 12/2/2025 9:37:54 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP4 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 12/2/2025 7:10:35 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.672.0) - Current Channel (Broad) Information 12/2/2025 6:54:49 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.672.0) - Current Channel (Broad) Information 12/2/2025 6:54:49 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/2/2025 4:49:59 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/2/2025 3:14:47 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/2/2025 3:12:42 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/2/2025 1:02:12 PM Service Control Manager 7045 None "A service was installed in the system. Service Name: Google Updater Service (GoogleUpdaterService144.0.7547.0) Service File Name: ""C:\Program Files (x86)\Google\GoogleUpdater\144.0.7547.0\updater.exe"" --system --windows-service --service=update Service Type: user mode service Service Start Type: auto start Service Account: LocalSystem" Information 12/2/2025 12:00:00 PM EventLog 6013 None The system uptime is 179338 seconds. Information 12/2/2025 11:59:58 AM EventLog 6013 None The system uptime is 179336 seconds. Information 12/2/2025 11:57:09 AM Service Control Manager 7045 None "A service was installed in the system. Service Name: Google Updater Internal Service (GoogleUpdaterInternalService144.0.7547.0) Service File Name: ""C:\Program Files (x86)\Google\GoogleUpdater\144.0.7547.0\updater.exe"" --system --windows-service --service=update-internal Service Type: user mode service Service Start Type: auto start Service Account: LocalSystem" Warning 12/2/2025 11:32:22 AM Tcpip 4205 None Autoconfigured route limit has been reached. No further autoconfigured routes will be added until the interface is reconnected. Information 12/2/2025 10:22:59 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.659.0) - Current Channel (Broad) Information 12/2/2025 10:21:54 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.659.0) - Current Channel (Broad) Information 12/2/2025 10:21:54 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Warning 12/2/2025 10:12:12 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 12/2/2025 10:12:12 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 12/2/2025 10:12:12 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 12/2/2025 10:12:12 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Information 12/2/2025 7:43:51 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/2/2025 2:44:36 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/2/2025 2:42:23 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/2/2025 1:45:44 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/2/2025 1:43:39 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/1/2025 10:37:43 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/1/2025 8:03:47 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.645.0) - Current Channel (Broad) Information 12/1/2025 8:03:23 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.645.0) - Current Channel (Broad) Information 12/1/2025 8:03:23 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/1/2025 3:14:41 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/1/2025 3:12:36 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/1/2025 1:31:35 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/1/2025 12:37:43 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRFJBH4-Microsoft.Windows.Photos Information 12/1/2025 12:37:40 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.Photos_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 12/1/2025 12:37:39 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRFJBH4-Microsoft.Windows.Photos Information 12/1/2025 12:37:33 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.Windows.Photos_2025.11110.18001.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 12/1/2025 12:36:19 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/1/2025 12:00:00 PM EventLog 6013 None The system uptime is 92938 seconds. Information 12/1/2025 11:59:58 AM EventLog 6013 None The system uptime is 92936 seconds. Information 12/1/2025 10:22:11 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.634.0) - Current Channel (Broad) Information 12/1/2025 10:21:56 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.634.0) - Current Channel (Broad) Information 12/1/2025 10:21:56 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Warning 12/1/2025 10:12:14 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86416 seconds since the last report. Warning 12/1/2025 10:12:14 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86416 seconds since the last report. Warning 12/1/2025 10:12:14 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86416 seconds since the last report. Warning 12/1/2025 10:12:14 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86416 seconds since the last report. Information 12/1/2025 4:25:27 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 12/1/2025 3:51:23 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/1/2025 3:49:10 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 12/1/2025 2:22:52 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.627.0) - Current Channel (Broad) Information 12/1/2025 2:22:36 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.627.0) - Current Channel (Broad) Information 12/1/2025 2:22:36 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 12/1/2025 1:45:45 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 12/1/2025 1:43:40 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/30/2025 10:46:15 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.612.0) - Current Channel (Broad) Information 11/30/2025 7:19:19 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/30/2025 3:14:36 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/30/2025 3:12:31 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/30/2025 12:00:00 PM EventLog 6013 None The system uptime is 6538 seconds. Information 11/30/2025 11:21:59 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/30/2025 11:04:55 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/30/2025 10:47:51 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/30/2025 10:30:47 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/30/2025 10:30:15 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRFHWLH-AD2F1837.HPPRINTERCONTROL Information 11/30/2025 10:30:13 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRFHWLH-AD2F1837.HPPRINTERCONTROL Information 11/30/2025 10:30:10 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\AD2F1837.HPPrinterControl_162.2.1122.0_x64__v10z8vjag6ke6\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/30/2025 10:28:55 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRD29V9-MICROSOFT.MICROSOFTOFFICEHUB Information 11/30/2025 10:28:54 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/30/2025 10:28:53 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRD29V9-MICROSOFT.MICROSOFTOFFICEHUB Information 11/30/2025 10:28:51 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.MicrosoftOfficeHub_19.2511.50071.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/30/2025 10:27:23 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9N5TDP8VCMHS-Microsoft.WebMediaExtensions Information 11/30/2025 10:27:22 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.WebMediaExtensions_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/30/2025 10:27:22 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9N5TDP8VCMHS-Microsoft.WebMediaExtensions Information 11/30/2025 10:27:20 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.WebMediaExtensions_1.2.17.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/30/2025 10:27:14 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/30/2025 10:27:08 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay Information 11/30/2025 10:27:06 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay Information 11/30/2025 10:27:04 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.XboxGamingOverlay_7.325.11061.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/30/2025 10:26:42 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/30/2025 10:26:42 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/30/2025 10:26:42 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/30/2025 10:26:29 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/30/2025 10:24:33 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Information 11/30/2025 10:24:25 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/30/2025 10:24:08 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/30/2025 10:23:49 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Information 11/30/2025 10:22:38 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\System32\SMI\Store\Machine\SCHEMA.DAT was cleared updating 1 keys and creating 1 modified pages. Information 11/30/2025 10:22:32 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/30/2025 10:22:31 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Information 11/30/2025 10:22:27 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-Provisioning-Sequence.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/30/2025 10:22:21 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/30/2025 10:21:43 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Warning 11/30/2025 10:16:48 AM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Error 11/30/2025 10:15:59 AM Microsoft-Windows-TPM-WMI 1801 None "Secure Boot CA/keys need to be updated. This device signature information is included here. DeviceAttributes: BaseBoardManufacturer:INTEL Corporation;FirmwareManufacturer:American Megatrends Inc.;FirmwareVersion:5.6.5;OEMModelNumber:To be filled by O.E.M.;OEMModelBaseBoard:CRESCENTBAY;OEMModelSystemFamily:To be filled by O.E.M.;OEMManufacturerName:To be filled by O.E.M.;OEMModelSKU:To be filled by O.E.M.;OSArchitecture:amd64; BucketId: 3172bfdf51002a90ec09ce6a4c3dd16df4a8a200aa84b1d0136a4916f76764e2 BucketConfidenceLevel: UpdateType: 0 HResult: The operation completed successfully." Information 11/30/2025 10:15:11 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/30/2025 10:13:43 AM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎30T18:13:43.478121900Z from ‎2025‎-‎11‎-‎30T18:13:43.477025500Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 8860)." Information 11/30/2025 10:13:43 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/30/2025 10:13:43 AM Microsoft-Windows-Time-Service 35 None The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123) with reference id 494637363. Current local stratum number is 4. Information 11/30/2025 10:13:43 AM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎30T18:13:43.477025500Z from ‎2025‎-‎11‎-‎30T18:13:25.717756800Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 8860)." Information 11/30/2025 10:13:43 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/30/2025 10:13:12 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 2 keys and creating 1 modified pages. Information 11/30/2025 10:13:11 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/30/2025 10:13:11 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\4820c8662999206_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Warning 11/30/2025 10:13:09 AM 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.WscBrokerManager 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." Warning 11/30/2025 10:13:09 AM 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.SecurityAppBroker 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." Warning 11/30/2025 10:13:09 AM 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." Information 11/30/2025 10:13:09 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/30/2025 10:13:08 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\Settings\settings.dat was cleared updating 12326 keys and creating 370 modified pages. Information 11/30/2025 10:12:44 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/30/2025 10:12:25 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.612.0) - Current Channel (Broad) Information 11/30/2025 10:12:09 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\AD2F1837.HPPrinterControl_v10z8vjag6ke6\Settings\settings.dat was cleared updating 3 keys and creating 1 modified pages. Information 11/30/2025 10:12:05 AM Microsoft-Windows-WER-SystemErrorReporting 1018 None The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space. Information 11/30/2025 10:12:03 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.612.0) - Current Channel (Broad) Information 11/30/2025 10:12:00 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\System32\config\COMPONENTS was cleared updating 86884 keys and creating 9973 modified pages. Warning 11/30/2025 10:11:58 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/30/2025 10:11:58 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/30/2025 10:11:58 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/30/2025 10:11:58 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Information 11/30/2025 10:11:54 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\c75fb7e1f4b8ebe1_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/30/2025 10:11:54 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 5 keys and creating 1 modified pages. Information 11/30/2025 10:11:51 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/30/2025 10:11:34 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 4 keys and creating 2 modified pages. Error 11/30/2025 10:11:34 AM Microsoft-Windows-WER-SystemErrorReporting 1001 None The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x000000000000003f, 0x00000000001722bb, 0x00000000558e25ed, 0x000000006f4ce49c). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 4850184e-655c-4ea1-b526-8782d78c59d4. Error 11/30/2025 10:11:32 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Warning 11/30/2025 10:11:29 AM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 11/30/2025 10:11:29 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat was cleared updating 2 keys and creating 1 modified pages. Information 11/30/2025 10:11:28 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\Settings\settings.dat was cleared updating 2 keys and creating 1 modified pages. Information 11/30/2025 10:11:22 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization\State\dosvcState.dat was cleared updating 11 keys and creating 3 modified pages. Information 11/30/2025 10:11:21 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\microsoft.windows.search_cw5n1h2txyewy\AC\GEH\POF.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/30/2025 10:11:20 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.Search_cw5n1h2txyewy\Settings\settings.dat was cleared updating 36 keys and creating 7 modified pages. Information 11/30/2025 10:11:19 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\Settings\settings.dat was cleared updating 3 keys and creating 1 modified pages. Warning 11/30/2025 10:11:12 AM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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 11/30/2025 10:11:12 AM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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." Information 11/30/2025 10:11:08 AM Service Control Manager 7026 None "The following boot-start or system-start driver(s) did not load: dam" Information 11/30/2025 10:11:06 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\AppCompat\Programs\Amcache.hve was cleared updating 1349 keys and creating 527 modified pages. Information 11/30/2025 10:11:04 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Microsoft\Windows\UsrClass.dat was cleared updating 3313 keys and creating 496 modified pages. Information 11/30/2025 10:11:04 AM Microsoft-Windows-Kernel-General 15 (10) Hive \??\C:\Users\User\ntuser.dat was reorganized with a starting size of 3379200 bytes and an ending size of 2461696 bytes. Error 11/30/2025 10:11:03 AM Service Control Manager 7034 None The MediaMTX service terminated unexpectedly. It has done this 1 time(s). Error 11/30/2025 10:11:03 AM Service Control Manager 7024 None "The MediaMTX service terminated with the following service-specific error: The system cannot find the path specified." Information 11/30/2025 10:11:03 AM Microsoft-Windows-Winlogon 7001 (1101) User Logon Notification for Customer Experience Improvement Program Information 11/30/2025 10:11:01 AM Microsoft-Windows-WLAN-AutoConfig 4000 None "WLAN AutoConfig service has successfully started. " Information 11/30/2025 10:10:59 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\bbimigrate\BBI was cleared updating 1 keys and creating 1 modified pages. Information 11/30/2025 10:10:58 AM Microsoft-Windows-DHCPv6-Client 51046 Service State Event DHCPv6 client service is started Information 11/30/2025 10:10:58 AM Microsoft-Windows-Dhcp-Client 50103 Service State Event DHCPv4 client registered for shutdown notification Information 11/30/2025 10:10:58 AM Microsoft-Windows-Dhcp-Client 50036 Service State Event DHCPv4 client service is started Information 11/30/2025 10:10:58 AM Microsoft-Windows-FilterManager 6 None File System Filter 'bindflt' (10.0, ‎2091‎-‎04‎-‎15T15:55:03.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:58 AM Microsoft-Windows-FilterManager 6 None File System Filter 'storqosflt' (10.0, ‎2038‎-‎12‎-‎03T01:18:20.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:58 AM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:58 AM Microsoft-Windows-FilterManager 1 None File System Filter 'CldFlt' (Version 10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) unloaded successfully. Information 11/30/2025 10:10:58 AM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:58 AM Microsoft-Windows-FilterManager 6 None File System Filter 'luafv' (10.0, ‎1996‎-‎01‎-‎27T04:16:28.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:58 AM Microsoft-Windows-FilterManager 6 None File System Filter 'wcifs' (10.0, ‎2043‎-‎11‎-‎04T03:04:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:57 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\ServiceProfiles\LocalService\NTUSER.DAT was cleared updating 71 keys and creating 16 modified pages. Information 11/30/2025 10:10:57 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\BBI was cleared updating 527 keys and creating 95 modified pages. Information 11/30/2025 10:10:57 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\ServiceProfiles\NetworkService\NTUSER.DAT was cleared updating 93 keys and creating 12 modified pages. Information 11/30/2025 10:10:56 AM Microsoft-Windows-Directory-Services-SAM 16983 None "The security account manager is now logging periodic summary events for remote clients that call legacy password change or set RPC methods. For more information please see https://go.microsoft.com/fwlink/?linkid=2150956. " Information 11/30/2025 10:10:56 AM Microsoft-Windows-Directory-Services-SAM 16977 None "The domain is configured with the following minimum password length-related settings. MinimumPasswordLength: 0 RelaxMinimumPasswordLengthLimits: 0 MinimumPasswordLengthAudit: -1 For more information see https://go.microsoft.com/fwlink/?LinkId=2097191. " Information 11/30/2025 10:10:56 AM Microsoft-Windows-Directory-Services-SAM 16962 None "Remote calls to the SAM database are being restricted using the default security descriptor: O:SYG:SYD:(A;;RC;;;BA). For more information please see http://go.microsoft.com/fwlink/?LinkId=787651." Information 11/30/2025 10:10:56 AM Microsoft-Windows-Wininit 14 None Credential Guard configuration: 0x0, 0 Information 11/30/2025 10:10:53 AM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection #2 Network link has been established at 1Gbps full duplex. " Information 11/30/2025 10:10:53 AM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection Network link has been established at 1Gbps full duplex. " Warning 11/30/2025 10:10:53 AM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 11/30/2025 10:10:53 AM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Information 11/30/2025 10:10:51 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \Device\HarddiskVolume2\EFI\Microsoft\Boot\BCD was cleared updating 61 keys and creating 8 modified pages. Information 11/30/2025 10:10:50 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/30/2025 10:10:50 AM Microsoft-Windows-Kernel-General 15 (10) Hive \SystemRoot\System32\Config\SOFTWARE was reorganized with a starting size of 84291584 bytes and an ending size of 81326080 bytes. Warning 11/30/2025 10:10:49 AM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Warning 11/30/2025 10:10:49 AM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Information 11/30/2025 10:10:47 AM NETwNe64 7036 None The \Device\NDMP4 service entered the Intel(R) Centrino(R) Wireless-N 2230 #2 state. Information 11/30/2025 10:10:47 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 3 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/30/2025 10:10:47 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 1 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/30/2025 10:10:47 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 2 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/30/2025 10:10:47 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 0 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/30/2025 10:10:47 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\DEFAULT was cleared updating 486 keys and creating 76 modified pages. Information 11/30/2025 10:10:47 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\SECURITY was cleared updating 75 keys and creating 4 modified pages. Information 11/30/2025 10:10:47 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\SAM was cleared updating 69 keys and creating 8 modified pages. Information 11/30/2025 10:10:47 AM Microsoft-Windows-Ntfs 98 None Volume \\?\Volume{df4bd8a4-f614-4d33-bbb6-6885459a0935} (\Device\HarddiskVolume1) is healthy. No action is needed. Information 11/30/2025 10:10:47 AM Microsoft-Windows-Ntfs 98 None Volume D: (\Device\HarddiskVolume5) is healthy. No action is needed. Information 11/30/2025 10:10:46 AM Microsoft-Windows-Kernel-Power 172 (203) Connectivity state in standby: Disconnected, Reason: NIC compliance Critical 11/30/2025 10:10:46 AM 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. Information 11/30/2025 10:10:46 AM Microsoft-Windows-FilterManager 6 None File System Filter 'npsvctrig' (10.0, ‎2025‎-‎01‎-‎05T18:41:12.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:46 AM Microsoft-Windows-FilterManager 6 None File System Filter 'UCPD' (10.0, ‎2006‎-‎08‎-‎28T03:56:22.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:46 AM Microsoft-Windows-FilterManager 6 None File System Filter 'FileCrypt' (10.0, ‎2002‎-‎03‎-‎01T03:12:42.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:46 AM Microsoft-Windows-Ntfs 98 None Volume C: (\Device\HarddiskVolume4) is healthy. No action is needed. Information 11/30/2025 10:10:45 AM Microsoft-Windows-FilterManager 6 None File System Filter 'WdFilter' (10.0, ‎2029‎-‎01‎-‎09T21:59:29.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:45 AM Microsoft-Windows-FilterManager 6 None File System Filter 'Wof' (10.0, ‎2090‎-‎03‎-‎16T10:56:17.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:45 AM Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (10.0, ‎2062‎-‎12‎-‎22T21:21:06.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/30/2025 10:10:45 AM Microsoft-Windows-HAL 16 None The iommu fault reporting has been initialized. Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-General 20 (6) "The leap second configuration has been updated. Reason: Leap second data initialized from registry during boot Leap seconds enabled: true New leap second count: 0 Old leap second count: 0" Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-Boot 30 (21) The firmware reported boot metrics. Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-Boot 32 (58) The bootmgr spent 0 ms waiting for user input. Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-Boot 18 (57) There are 0x1 boot options on this system. Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-Boot 27 (33) The boot type was 0x0. Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-Boot 25 (32) The boot menu policy was 0x1. Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-Boot 238 (101) EFI time zone bias: 2047. Daylight flags: 0 Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-Boot 20 (31) The last shutdown's success status was false. The last boot's success status was true. Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-Boot 153 (62) Virtualization-based security (policies: 0) is disabled. Information 11/30/2025 10:10:58 AM EventLog 6013 None The system uptime is 13 seconds. Information 11/30/2025 10:10:58 AM EventLog 6005 None The Event log service was started. Information 11/30/2025 10:10:58 AM EventLog 6009 None Microsoft (R) Windows (R) 10.00. 19045 Multiprocessor Free. Error 11/30/2025 10:10:58 AM EventLog 6008 None The previous system shutdown at 11:08:40 PM on ‎11/‎17/‎2025 was unexpected. Information 11/30/2025 10:10:45 AM Microsoft-Windows-Kernel-General 12 (1) The operating system started at system time ‎2025‎-‎11‎-‎30T18:10:44.500000000Z. Error 11/30/2025 9:49:49 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 9:49:48 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/30/2025 9:45:36 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 9:42:36 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 9:42:35 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 9:39:10 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 9:37:26 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 9:37:25 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 9:35:00 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 9:34:59 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 9:32:49 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 9:31:19 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 9:31:18 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 9:19:22 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/30/2025 9:17:31 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 8:47:39 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 8:47:39 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/30/2025 8:24:47 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 8:18:35 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 8:12:10 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 8:05:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 8:04:34 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 7:53:26 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 7:53:25 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/30/2025 7:48:03 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 7:35:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 7:03:43 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/30/2025 6:41:57 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 6:31:43 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 6:30:06 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 6:27:43 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 6:17:34 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 6:07:17 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 5:47:14 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 5:47:14 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 5:41:54 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 5:16:32 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/30/2025 5:14:32 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 5:14:31 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 4:50:49 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 4:50:49 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/30/2025 4:44:34 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 4:35:56 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 4:35:34 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 4:35:34 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/30/2025 4:34:57 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 4:34:55 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/30/2025 4:31:57 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 4:30:48 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 4:30:48 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/30/2025 4:23:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/30/2025 4:19:17 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 11/30/2025 4:13:43 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 4:07:28 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 4:07:25 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/30/2025 4:04:45 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 4:04:45 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/30/2025 4:04:24 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/30/2025 4:03:28 AM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/30/2025 3:58:14 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/30/2025 3:57:30 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 3:56:04 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 3:55:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Information 11/30/2025 3:54:06 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/30/2025 3:51:58 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Settings\settings.dat was cleared updating 5 keys and creating 1 modified pages. Error 11/30/2025 3:48:02 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/30/2025 3:48:02 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 3:48:02 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/30/2025 3:46:19 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 3:44:17 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 3:44:16 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 3:35:05 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 3:35:05 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 3:27:13 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 3:27:13 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 3:20:12 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/30/2025 3:18:29 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 3:18:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 3:09:37 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 3:03:26 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 2:50:57 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 2:50:54 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/30/2025 2:36:56 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 2:35:03 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/30/2025 2:29:44 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/30/2025 2:04:31 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 1:50:52 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 1:50:52 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/30/2025 1:47:37 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/30/2025 1:47:37 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 1:47:36 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/30/2025 1:46:42 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/30/2025 1:46:42 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 1:46:42 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/30/2025 1:42:43 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 1:42:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/30/2025 1:37:07 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 1:27:00 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 1:24:18 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/30/2025 1:24:18 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 1:24:16 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/30/2025 1:19:46 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 1:19:35 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/30/2025 1:14:52 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service LxpSvc with arguments ""Unavailable"" in order to run the server: {D0582E3B-3126-4CAA-9155-AC37C912A489}" Error 11/30/2025 1:14:44 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Language Experience Service service to connect. Error 11/30/2025 1:13:32 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 1:10:45 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 1:10:45 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 1:05:46 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 1:05:45 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/30/2025 12:55:43 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 11/30/2025 12:51:17 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 12:50:58 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 12:50:58 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/30/2025 12:41:09 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 12:38:57 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/30/2025 12:33:35 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!WindowsBackup.AppXqj224hkh7nbp78xkn6xxwg6waga3cft4.mca did not register with DCOM within the required timeout. Error 11/30/2025 12:26:27 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 12:25:56 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 12:25:55 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 12:16:03 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 12:16:03 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 12:10:57 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 12:10:57 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/30/2025 12:04:03 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/30/2025 12:02:06 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 12:02:06 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/30/2025 12:02:06 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/30/2025 12:02:06 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 11:52:32 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 11:52:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/29/2025 11:52:05 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 11:50:58 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 11:50:58 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/29/2025 11:45:54 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 11:38:48 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 11:27:04 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 11:21:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Warning 11/29/2025 11:09:25 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/29/2025 11:09:25 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/29/2025 11:09:25 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/29/2025 11:09:25 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 11/29/2025 11:09:19 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 11:05:20 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 10:59:10 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 10:55:10 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 10:51:10 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 10:41:03 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 10:03:57 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 9:41:36 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 9:23:49 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 9:23:49 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 9:21:04 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 9:10:18 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 8:59:02 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 8:48:48 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 8:47:31 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 8:47:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 8:46:41 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 8:46:41 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 8:40:33 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 8:40:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 8:35:53 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 8:35:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 8:33:04 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 8:25:56 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 8:25:56 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 8:20:55 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 8:20:55 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 8:10:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 7:58:30 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 7:51:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 7:46:05 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 7:46:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/29/2025 7:20:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 7:14:02 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 6:58:03 PM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 11/29/2025 6:20:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 6:15:58 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 6:09:49 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 6:05:49 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 6:00:02 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 6:00:02 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 5:43:49 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Wallet_2.4.18324.0_x64__8wekyb3d8bbwe!App.AppXgvxkrr1tm1jwgecmqbxe81yfbwpjdn1h.mca did not register with DCOM within the required timeout. Error 11/29/2025 5:39:27 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 5:33:01 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 5:33:00 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/29/2025 5:23:31 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/29/2025 5:16:55 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 5:16:55 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 5:16:55 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 5:10:21 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 3:43:32 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 3:34:26 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:34:26 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/29/2025 3:15:19 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Information 11/29/2025 3:14:28 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 11/29/2025 3:07:48 PM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/29/2025 3:05:34 PM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Information 11/29/2025 3:03:40 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/29/2025 3:01:41 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:01:40 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/29/2025 2:55:33 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 2:50:48 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 2:50:48 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/29/2025 2:39:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 2:32:23 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 2:32:23 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 2:32:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 2:24:49 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 2:24:49 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 2:24:48 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 2:06:21 PM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/29/2025 1:55:08 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:55:08 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 1:50:16 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:50:14 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 1:44:36 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 1:25:16 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 1:24:48 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:24:48 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 1:15:51 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:15:50 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 1:15:10 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:15:10 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 1:10:11 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:10:10 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:58:14 PM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/29/2025 12:58:05 PM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 11/29/2025 12:53:46 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:53:46 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:48:57 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:48:56 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:47:59 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:47:59 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:44:29 PM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/29/2025 12:42:58 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:42:58 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:35:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 12:25:17 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:25:17 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:24:58 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 12:24:28 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:24:27 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:19:14 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:19:14 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:18:36 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:18:36 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:09:37 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:09:37 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:00:51 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:00:51 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/29/2025 12:00:00 PM EventLog 6013 None The system uptime is 996684 seconds. Error 11/29/2025 11:53:09 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 11:51:46 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 11:51:46 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 11:36:08 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 11:27:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 10:58:12 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 10:55:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 10:52:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 10:49:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 10:42:56 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 10:03:48 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 9:57:24 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.IrisService.AppXwwah2tbqj7j749pkqvs0hna8en4npvp8.mca did not register with DCOM within the required timeout. Error 11/29/2025 9:51:52 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 9:50:24 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 9:50:24 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 9:41:42 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 9:41:42 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 9:32:39 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 9:32:39 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 9:31:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 9:22:28 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 8:53:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 8:50:49 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 8:50:49 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/29/2025 8:32:47 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/29/2025 8:17:18 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/29/2025 7:32:17 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 6:50:33 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 6:49:42 AM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Error 11/29/2025 6:49:09 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {4991D34B-80A1-4291-83B6-3328366B9097}" Error 11/29/2025 6:49:09 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 6:49:09 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Information 11/29/2025 6:47:38 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.YourPhone_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\d4be7e4a3deb5b23_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Error 11/29/2025 6:40:01 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/29/2025 6:35:25 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.YourPhone_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 46 keys and creating 5 modified pages. Error 11/29/2025 6:09:37 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 6:09:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 6:00:37 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 6:00:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 5:50:43 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 5:50:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/29/2025 5:03:47 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 4:53:26 AM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 4:53:25 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/29/2025 4:50:52 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 4:50:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/29/2025 4:14:01 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 4:14:01 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/29/2025 4:09:21 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 4:09:21 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/29/2025 4:06:06 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.Accounts.AppXczw5m0gs1v24mkf1zqkkpebvayhcn73d.mca did not register with DCOM within the required timeout. Error 11/29/2025 4:04:16 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 4:04:15 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/29/2025 3:56:38 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/29/2025 3:44:16 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/29/2025 3:41:43 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/29/2025 3:37:06 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/29/2025 3:37:06 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:37:00 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/29/2025 3:36:54 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:36:54 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 3:35:50 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/29/2025 3:35:50 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:35:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/29/2025 3:31:50 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:31:49 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 3:28:57 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/29/2025 3:28:57 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:28:56 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/29/2025 3:23:49 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:23:48 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 3:20:30 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/29/2025 3:20:30 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:20:29 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/29/2025 3:16:47 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:16:47 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 3:16:05 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:16:03 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 3:13:33 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:13:33 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 3:11:07 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 3:11:07 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/29/2025 3:07:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 3:06:08 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 3:05:20 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 2:59:19 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 2:53:12 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/29/2025 2:51:56 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 2:10:36 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 2:10:36 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 2:10:35 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 2:09:17 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 2:09:12 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 2:09:11 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 2:03:58 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 2:03:58 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 2:03:57 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 1:58:23 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 1:58:23 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:58:22 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 1:51:48 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 11/29/2025 1:51:48 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:51:47 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 1:33:49 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:33:49 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/29/2025 1:19:34 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 1:19:33 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/29/2025 1:16:08 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/29/2025 1:14:38 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service LxpSvc with arguments ""Unavailable"" in order to run the server: {D0582E3B-3126-4CAA-9155-AC37C912A489}" Error 11/29/2025 1:14:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Language Experience Service service to connect. Error 11/29/2025 12:47:31 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 12:45:03 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 12:43:50 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:43:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:42:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 12:37:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 12:33:06 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 12:25:57 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 12:25:57 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:25:57 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 12:25:06 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 12:21:13 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 12:21:13 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:21:13 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 12:21:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 12:16:41 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:16:41 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:12:41 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 12:12:40 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:12:39 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 12:12:25 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/29/2025 12:10:57 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/29/2025 12:07:59 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/29/2025 12:07:59 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:07:59 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/29/2025 12:07:43 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:07:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/29/2025 12:06:58 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/29/2025 12:06:58 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 11:57:53 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 11:57:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 11:46:50 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 11:46:50 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/28/2025 11:11:16 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Information 11/28/2025 11:11:09 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/28/2025 11:10:03 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Warning 11/28/2025 11:09:27 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/28/2025 11:09:27 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/28/2025 11:09:27 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/28/2025 11:09:27 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 11/28/2025 10:33:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 10:26:57 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 10:26:56 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/28/2025 10:22:54 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 9:57:49 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 9:25:37 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 9:23:18 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 9:23:18 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/28/2025 9:13:39 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 8:53:38 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 8:43:27 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 8:13:22 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 7:41:27 PM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 7:41:27 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/28/2025 7:35:28 PM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 7:35:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/28/2025 7:34:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 7:25:26 PM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 7:25:25 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/28/2025 7:24:42 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 7:19:48 PM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 7:19:45 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/28/2025 7:15:06 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/28/2025 7:13:34 PM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 7:13:33 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/28/2025 7:08:03 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 7:08:03 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/28/2025 7:05:05 PM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 11/28/2025 7:02:29 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 7:02:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/28/2025 6:57:49 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 6:57:49 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/28/2025 6:57:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 6:46:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 6:40:17 PM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.RulesEngine.AppXg6p1s9373bk1gyjynwzsms4dqcb1sqz1.mca did not register with DCOM within the required timeout. Error 11/28/2025 6:28:16 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.YourPhone_1.25072.79.0_x64__8wekyb3d8bbwe!App.AppXn958k7nsj8mxxmsepqdam8xk948t30sc.mca did not register with DCOM within the required timeout. Error 11/28/2025 6:25:29 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 6:25:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 6:19:39 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 6:19:38 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 6:10:39 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 6:10:39 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 6:05:55 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 6:05:55 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 6:01:08 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 6:01:08 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 5:43:04 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 5:43:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 5:34:04 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 5:34:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 5:33:22 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 5:33:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 5:32:22 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 5:32:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 3:51:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 3:39:43 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 3:27:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 3:17:00 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/28/2025 3:16:59 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 3:16:59 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/28/2025 3:12:10 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/28/2025 3:12:10 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 3:12:10 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/28/2025 3:07:28 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/28/2025 3:07:28 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 3:07:27 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/28/2025 3:03:09 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/28/2025 3:03:09 PM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 3:03:08 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/28/2025 3:02:39 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/28/2025 3:02:39 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:59:48 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/28/2025 2:58:48 PM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/28/2025 2:57:23 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:57:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/28/2025 2:56:13 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:56:13 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/28/2025 2:50:57 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/28/2025 2:50:57 PM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:50:57 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/28/2025 2:48:44 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/28/2025 2:48:44 PM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:48:44 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/28/2025 2:46:04 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 2:40:39 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:40:39 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 2:26:27 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:26:26 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 2:25:26 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:25:26 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 2:20:48 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:20:47 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 2:15:57 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:15:57 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 2:14:59 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 2:11:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Information 11/28/2025 2:05:01 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/28/2025 1:58:54 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 1:49:35 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 1:49:35 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 1:45:38 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 1:30:53 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 1:13:29 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 1:08:51 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 1:08:51 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 1:03:50 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 1:03:50 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 12:59:19 PM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 11/28/2025 12:57:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 12:34:31 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 12:11:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 12:06:50 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/28/2025 12:00:00 PM EventLog 6013 None The system uptime is 910286 seconds. Information 11/28/2025 11:59:58 AM EventLog 6013 None The system uptime is 910284 seconds. Error 11/28/2025 10:52:51 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 10:52:06 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 10:52:06 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 10:43:07 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 10:43:06 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 10:33:47 AM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/28/2025 10:29:38 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 10:27:26 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 10:13:14 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 10:09:18 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 10:09:18 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 10:04:15 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 10:04:15 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 10:03:31 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 10:03:31 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 10:03:03 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 9:54:26 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 9:54:26 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 9:49:21 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 9:42:25 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 9:35:16 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 9:35:16 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 9:26:22 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 9:26:22 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 8:32:39 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 8:32:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/28/2025 8:24:37 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 8:20:36 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 8:10:26 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 7:42:48 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 7:33:57 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 7:12:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/28/2025 7:09:48 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 6:50:40 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 6:50:40 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/28/2025 6:48:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 6:04:31 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.YourPhone_1.25072.79.0_x64__8wekyb3d8bbwe!App.AppXn958k7nsj8mxxmsepqdam8xk948t30sc.mca did not register with DCOM within the required timeout. Error 11/28/2025 6:01:59 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 6:01:59 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/28/2025 6:01:18 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 6:01:17 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/28/2025 5:56:31 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 5:56:31 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 11/28/2025 4:58:52 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/28/2025 4:41:50 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 4:18:55 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 4:18:55 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 4:18:13 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 4:18:12 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 4:09:17 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 4:09:16 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 4:06:34 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 3:43:55 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 3:43:55 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 3:40:27 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/28/2025 3:27:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 3:27:54 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 3:27:54 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 3:25:48 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 3:21:49 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 3:18:51 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 3:18:51 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/28/2025 3:16:45 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 11/28/2025 3:13:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/28/2025 3:11:45 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Information 11/28/2025 3:10:07 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/28/2025 3:09:12 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/28/2025 3:09:11 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 3:09:11 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/28/2025 3:04:51 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 2:54:34 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 2:50:38 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:50:38 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/28/2025 2:28:19 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 2:28:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 1:45:51 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 1:33:03 AM Service Control Manager 7000 None "The Device Setup Manager service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 1:33:03 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Device Setup Manager service to connect. Error 11/28/2025 1:19:59 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 1:19:58 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/28/2025 1:10:44 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service LxpSvc with arguments ""Unavailable"" in order to run the server: {D0582E3B-3126-4CAA-9155-AC37C912A489}" Error 11/28/2025 1:10:44 AM Service Control Manager 7000 None "The Device Setup Manager service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 1:10:44 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Device Setup Manager service to connect. Error 11/28/2025 1:10:44 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Language Experience Service service to connect. Error 11/28/2025 1:02:40 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/28/2025 12:32:56 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/28/2025 12:15:22 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 12:15:22 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 12:14:42 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 12:14:42 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 12:05:42 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/28/2025 12:05:42 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/28/2025 12:02:45 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Warning 11/27/2025 11:09:29 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86394 seconds since the last report. Warning 11/27/2025 11:09:29 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86394 seconds since the last report. Warning 11/27/2025 11:09:29 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86394 seconds since the last report. Warning 11/27/2025 11:09:29 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86394 seconds since the last report. Error 11/27/2025 10:52:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 10:48:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 10:37:55 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 9:48:24 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 9:24:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 9:20:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 9:18:51 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/27/2025 8:46:40 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:46:39 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Information 11/27/2025 8:08:47 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 11/27/2025 8:08:47 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 11/27/2025 8:02:56 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 7:52:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/27/2025 7:52:38 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/27/2025 7:51:21 PM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 7:51:20 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/27/2025 7:45:48 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 6:50:28 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 6:50:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 6:40:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 6:04:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 5:51:12 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 5:51:12 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 5:46:29 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 5:46:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 5:42:23 PM Service Control Manager 7000 None "The Connected User Experiences and Telemetry service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 5:42:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Connected User Experiences and Telemetry service to connect. Error 11/27/2025 5:03:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 4:50:29 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 4:50:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 4:46:07 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 4:46:07 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 3:50:32 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:50:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 3:46:43 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 3:42:19 PM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:42:19 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/27/2025 3:22:05 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:22:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 3:15:45 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:15:43 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 3:11:12 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/27/2025 3:11:07 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:11:07 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 3:02:07 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:02:07 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 3:01:28 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:01:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 3:00:54 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 2:56:23 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:56:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 2:43:31 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/27/2025 2:43:31 PM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:43:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/27/2025 2:38:11 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/27/2025 2:38:11 PM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:38:11 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/27/2025 2:33:54 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:33:54 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/27/2025 2:32:48 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 2:31:09 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/27/2025 2:31:09 PM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:31:09 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/27/2025 2:25:04 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/27/2025 2:25:04 PM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:25:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/27/2025 2:24:14 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:24:14 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 2:22:42 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 2:17:57 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:17:57 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 2:11:29 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:11:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 2:09:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 2:03:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 2:02:51 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/27/2025 2:02:51 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:02:50 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/27/2025 2:01:49 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:01:49 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 1:58:31 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 1:58:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 1:07:45 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 12:59:42 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 12:53:55 PM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 11/27/2025 12:50:28 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 12:50:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 12:20:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 12:04:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/27/2025 12:00:00 PM EventLog 6013 None The system uptime is 823885 seconds. Information 11/27/2025 11:59:59 AM EventLog 6013 None The system uptime is 823884 seconds. Error 11/27/2025 11:50:26 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 11:50:26 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 11:32:29 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 11:24:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/27/2025 10:46:29 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/27/2025 10:27:49 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 10:16:15 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 10:08:03 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 9:50:32 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 9:50:32 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 9:45:55 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.IrisService.AppXwwah2tbqj7j749pkqvs0hna8en4npvp8.mca did not register with DCOM within the required timeout. Error 11/27/2025 9:45:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/27/2025 9:30:51 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 9:30:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 9:26:12 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 9:26:12 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/27/2025 9:25:33 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 9:25:31 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 9:24:41 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 9:12:40 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 9:02:27 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 9:01:02 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 9:01:02 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 8:48:48 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:48:48 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 8:47:09 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:47:09 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 8:45:59 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:45:58 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 8:41:00 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:40:59 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 8:40:21 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:40:21 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 8:38:15 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:38:15 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 8:32:31 AM Microsoft-Windows-DistributedCOM 10010 None The server Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager did not register with DCOM within the required timeout. Error 11/27/2025 8:32:00 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:31:59 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 8:31:19 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:31:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 8:30:29 AM Microsoft-Windows-DistributedCOM 10010 None The server Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager did not register with DCOM within the required timeout. Error 11/27/2025 8:28:27 AM Microsoft-Windows-DistributedCOM 10010 None The server Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager did not register with DCOM within the required timeout. Error 11/27/2025 8:27:26 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:27:26 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 8:15:16 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:15:16 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 8:04:37 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 8:04:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 7:55:36 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 7:55:35 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 7:50:23 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 7:50:23 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 7:19:34 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 5:58:19 AM Service Control Manager 7000 None "The Connected User Experiences and Telemetry service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 5:58:18 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Connected User Experiences and Telemetry service to connect. Error 11/27/2025 5:56:15 AM Service Control Manager 7031 None The Connected User Experiences and Telemetry service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. Information 11/27/2025 5:56:13 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\config\DRIVERS was cleared updating 29635 keys and creating 1606 modified pages. Error 11/27/2025 5:53:43 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 5:53:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 5:50:29 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 5:50:29 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 5:34:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 5:22:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 5:14:36 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/27/2025 5:10:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 5:08:17 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 5:08:17 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/27/2025 5:05:36 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 5:04:50 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 5:03:37 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 5:03:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/27/2025 4:53:44 AM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 4:53:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/27/2025 4:51:36 AM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 4:51:36 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/27/2025 4:47:22 AM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 4:47:21 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/27/2025 4:41:45 AM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 4:41:44 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/27/2025 4:39:32 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 4:35:23 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 4:35:23 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 4:29:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 4:23:33 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 11/27/2025 4:23:33 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 4:23:33 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/27/2025 4:19:16 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 4:08:01 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 4:00:03 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 11/27/2025 4:00:03 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 4:00:02 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/27/2025 3:48:42 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:48:42 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 3:46:53 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:46:53 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 3:45:54 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:45:54 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 3:33:54 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:33:54 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 3:31:57 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/27/2025 3:31:57 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:31:57 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 3:31:57 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:31:57 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/27/2025 3:29:00 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:29:00 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 3:18:52 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:18:51 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 3:18:44 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.CrossDevice_0.25072.59.0_x64__cw5n1h2txyewy!SettingsUXHostApp.AppXxnb2wgd17pheptmaxx5ykxp7bcmqe4ra.mca did not register with DCOM within the required timeout. Error 11/27/2025 3:18:44 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/27/2025 3:03:52 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/27/2025 3:03:51 AM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Information 11/27/2025 3:02:48 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 11/27/2025 3:02:21 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:02:21 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/27/2025 3:00:38 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 3:00:38 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 2:59:01 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/27/2025 2:56:39 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Information 11/27/2025 2:54:48 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/27/2025 2:50:27 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:50:26 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/27/2025 2:46:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 2:45:50 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:45:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 2:45:03 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:45:03 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 2:44:49 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 2:36:04 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 2:36:04 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/27/2025 2:13:41 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 1:49:30 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/27/2025 1:40:21 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/27/2025 1:37:18 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/27/2025 1:15:41 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/27/2025 1:14:10 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service LxpSvc with arguments ""Unavailable"" in order to run the server: {D0582E3B-3126-4CAA-9155-AC37C912A489}" Error 11/27/2025 1:14:10 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 11/27/2025 1:14:10 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 1:14:10 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Language Experience Service service to connect. Error 11/27/2025 1:14:10 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/27/2025 1:08:28 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 12:48:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 12:46:14 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 12:34:12 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/27/2025 12:02:25 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/27/2025 12:02:25 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Warning 11/26/2025 11:09:35 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Warning 11/26/2025 11:09:35 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Warning 11/26/2025 11:09:35 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Warning 11/26/2025 11:09:35 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Error 11/26/2025 10:50:37 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 10:50:36 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 10:47:26 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 10:45:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 10:43:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 10:39:06 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 10:36:54 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 9:50:29 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 9:50:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 9:21:56 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 8:57:23 PM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 8:57:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/26/2025 8:48:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 8:15:58 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 8:14:03 PM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.RulesEngine.AppXg6p1s9373bk1gyjynwzsms4dqcb1sqz1.mca did not register with DCOM within the required timeout. Error 11/26/2025 8:02:56 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 8:00:49 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 7:56:33 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 7:56:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/26/2025 7:50:56 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 7:48:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 7:25:30 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 6:50:22 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 6:50:22 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 6:50:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/26/2025 6:50:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 6:46:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 6:45:10 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 6:45:10 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 6:31:30 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 6:27:10 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 6:27:10 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 6:24:32 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 6:16:32 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 6:12:32 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 6:11:31 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.YourPhone_1.25072.79.0_x64__8wekyb3d8bbwe!App.AppXn958k7nsj8mxxmsepqdam8xk948t30sc.mca did not register with DCOM within the required timeout. Error 11/26/2025 6:07:25 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Wallet_2.4.18324.0_x64__8wekyb3d8bbwe!App.AppXgvxkrr1tm1jwgecmqbxe81yfbwpjdn1h.mca did not register with DCOM within the required timeout. Error 11/26/2025 6:03:20 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 5:56:19 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:56:19 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/26/2025 5:52:20 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:52:20 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 5:50:25 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:50:25 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 5:47:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 5:43:20 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:43:20 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:43:20 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 5:43:20 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/26/2025 5:42:39 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:42:39 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 5:33:41 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:33:41 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 5:23:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 5:22:46 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 5:20:13 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:20:13 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 5:11:13 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:11:13 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 5:10:31 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:10:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 5:01:36 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:01:36 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 4:46:22 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 4:46:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Information 11/26/2025 4:34:12 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/26/2025 4:20:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 3:33:23 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 3:33:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 3:28:21 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 3:28:21 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 3:10:07 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 3:10:06 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 3:07:05 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 3:07:05 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/26/2025 3:03:14 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/26/2025 3:03:12 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/26/2025 2:51:19 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 2:51:18 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 2:40:37 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/26/2025 2:25:40 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/26/2025 2:23:13 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/26/2025 2:17:15 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 2:01:14 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 1:50:29 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 1:50:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 1:39:32 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 1:39:32 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Warning 11/26/2025 1:18:58 PM Tcpip 4227 None TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint. Error 11/26/2025 1:10:15 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 12:50:09 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 12:50:09 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 12:48:18 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/26/2025 12:00:00 PM EventLog 6013 None The system uptime is 737486 seconds. Information 11/26/2025 11:59:59 AM EventLog 6013 None The system uptime is 737484 seconds. Error 11/26/2025 11:55:25 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 11:50:29 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 11:50:29 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 11:30:53 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 11/26/2025 10:54:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 10:29:39 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 9:15:43 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 9:11:43 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/26/2025 9:06:47 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\790b7f9a2cf25097_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Error 11/26/2025 9:01:35 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 8:51:24 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 8:44:54 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.4239_neutral_neutral_cw5n1h2txyewy!Windows.Networking.BackgroundTransfer.Internal.NetworkChangeTask.ClassId.1 did not register with DCOM within the required timeout. Error 11/26/2025 8:42:43 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 8:42:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 8:41:43 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 8:41:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 8:32:43 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 8:32:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 8:32:02 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 8:32:00 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 8:23:07 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 8:23:07 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 8:20:12 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 7:46:24 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 7:46:24 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 7:38:36 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Information 11/26/2025 7:28:03 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/26/2025 7:26:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/26/2025 7:21:02 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 7:14:50 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 7:14:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 7:04:11 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/26/2025 7:00:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 6:56:10 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 6:56:10 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 6:55:30 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 6:55:30 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 6:54:35 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 6:54:35 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 6:54:35 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 6:06:28 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 6:06:28 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/26/2025 5:58:55 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:58:54 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 5:49:52 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:49:52 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 5:46:19 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 5:46:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 5:14:31 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/26/2025 4:59:45 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 4:43:36 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 4:19:36 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 4:13:29 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 4:03:21 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 3:29:10 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 3:29:10 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 3:26:08 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 3:18:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 3:10:47 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 3:10:47 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 3:01:45 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 3:01:45 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/26/2025 2:56:19 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/26/2025 2:54:00 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/26/2025 2:50:13 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 2:50:13 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 2:27:22 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/26/2025 2:04:09 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 1:52:43 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 1:50:12 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 1:50:12 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 12:59:46 AM Microsoft-Windows-DistributedCOM 10010 None The server microsoft.windowscommunicationsapps_16005.14326.22342.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout. Information 11/26/2025 12:57:49 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 27 keys and creating 3 modified pages. Error 11/26/2025 12:57:19 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 12:57:18 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/26/2025 12:54:08 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 12:50:10 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 12:50:10 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/26/2025 12:47:52 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/26/2025 12:10:53 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 12:10:52 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/26/2025 12:01:53 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/26/2025 12:01:53 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 11:19:27 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 11:19:26 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 11:13:57 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 11:11:50 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Warning 11/25/2025 11:09:33 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/25/2025 11:09:33 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/25/2025 11:09:33 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/25/2025 11:09:33 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 11/25/2025 10:48:19 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/25/2025 10:21:55 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/25/2025 9:42:33 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 9:06:40 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 8:54:31 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 8:50:15 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 8:50:15 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/25/2025 8:35:08 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 8:35:08 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 8:34:27 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 8:26:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 7:09:11 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 7:09:11 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 6:55:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 6:51:40 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 6:50:14 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 6:50:13 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/25/2025 6:43:23 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 6:23:26 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 6:12:33 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 6:08:07 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.YourPhone_1.25072.79.0_x64__8wekyb3d8bbwe!App.AppXn958k7nsj8mxxmsepqdam8xk948t30sc.mca did not register with DCOM within the required timeout. Error 11/25/2025 6:04:47 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 6:04:47 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 5:55:48 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 5:55:47 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 5:55:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 5:50:11 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 5:50:10 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/25/2025 5:06:13 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 5:02:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 4:56:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 4:52:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 4:28:15 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 4:22:05 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 3:56:49 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:56:49 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 3:55:18 PM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/25/2025 3:51:49 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:51:48 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 3:46:13 PM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/25/2025 3:20:57 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/25/2025 3:10:50 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:10:50 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 3:06:12 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:06:12 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 3:01:28 PM Microsoft-Windows-DistributedCOM 10010 None The server microsoft.windowscommunicationsapps_16005.14326.22342.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout. Error 11/25/2025 2:39:50 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 2:39:50 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/25/2025 2:20:51 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/25/2025 2:18:21 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/25/2025 2:17:03 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 2:06:51 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 1:52:05 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 1:42:51 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 1:32:34 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 1:20:33 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/25/2025 1:15:46 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/25/2025 12:50:07 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 12:46:10 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 12:46:10 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/25/2025 12:16:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/25/2025 12:00:00 PM EventLog 6013 None The system uptime is 651086 seconds. Information 11/25/2025 11:59:58 AM EventLog 6013 None The system uptime is 651083 seconds. Error 11/25/2025 11:50:06 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 11:50:06 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/25/2025 11:36:44 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 11:36:44 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 11:34:10 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 11:27:46 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 11:27:46 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 11:24:03 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 11:06:19 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 11:06:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/25/2025 10:46:04 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 10:46:03 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/25/2025 10:20:29 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 10:15:41 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 9:50:00 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 9:50:00 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/25/2025 9:48:18 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 9:46:12 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 9:30:11 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 9:29:51 AM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/25/2025 9:20:04 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 9:08:31 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 8:36:04 AM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 8:36:03 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/25/2025 8:33:21 AM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 8:33:20 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/25/2025 8:31:50 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 8:21:41 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 7:59:06 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 7:44:32 AM Service Control Manager 7000 None "The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 7:44:31 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. Error 11/25/2025 6:46:28 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 6:46:28 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 6:41:16 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 6:41:16 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/25/2025 6:39:16 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 6:21:26 AM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Error 11/25/2025 6:15:16 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 6:15:16 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/25/2025 6:05:15 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 6:05:14 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 5:51:14 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 5:50:09 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 5:50:09 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 5:46:09 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 5:41:05 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 5:41:05 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 5:36:56 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 5:36:55 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/25/2025 5:36:00 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 5:19:53 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/25/2025 5:12:51 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 5:12:51 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 5:06:27 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 5:06:27 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 5:03:50 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 5:03:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 4:57:26 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 4:57:26 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 4:56:48 AM Service Control Manager 7000 None "The Connected User Experiences and Telemetry service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 4:56:47 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Connected User Experiences and Telemetry service to connect. Error 11/25/2025 4:51:04 AM Service Control Manager 7031 None The Connected User Experiences and Telemetry service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. Error 11/25/2025 4:51:04 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 4:51:04 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/25/2025 4:47:04 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 4:47:04 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 4:42:46 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 4:40:09 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 4:40:08 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 4:38:47 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 4:36:53 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 4:36:53 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 4:30:27 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 4:30:27 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 4:23:01 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 4:18:41 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.RulesEngine.AppX5z5kfs8055rf6ttb3wq8ztd1bbgncvdy.mca did not register with DCOM within the required timeout. Error 11/25/2025 4:17:10 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.Accounts.AppXczw5m0gs1v24mkf1zqkkpebvayhcn73d.mca did not register with DCOM within the required timeout. Error 11/25/2025 4:14:39 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/25/2025 4:09:37 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/25/2025 4:05:24 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/25/2025 4:01:54 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 3:59:44 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 3:58:56 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:58:56 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 3:57:33 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 3:44:11 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:44:11 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 3:44:09 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:44:08 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 3:38:18 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:38:18 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 3:33:43 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:33:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 3:30:15 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 3:20:58 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:20:58 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 3:18:14 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 3:13:03 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:13:03 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 3:11:08 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Information 11/25/2025 3:09:20 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 11/25/2025 3:08:21 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 3:08:20 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 3:03:56 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 3:01:45 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 2:57:34 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 2:57:34 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/25/2025 2:55:35 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 2:53:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/25/2025 2:49:13 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/25/2025 2:47:26 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 2:47:08 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 2:45:03 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 2:42:50 AM Microsoft-Windows-DistributedCOM 10010 None The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. Error 11/25/2025 2:42:47 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 2:40:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 2:39:58 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/25/2025 2:39:57 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 2:39:56 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/25/2025 2:38:18 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 2:36:22 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 2:34:56 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/25/2025 2:34:55 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 2:34:55 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/25/2025 2:30:13 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 2:29:21 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 2:29:20 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 2:25:03 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/25/2025 2:25:03 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 2:25:02 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/25/2025 2:22:32 AM Service Control Manager 7034 None The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 3 time(s). Error 11/25/2025 2:21:50 AM Microsoft-Windows-DistributedCOM 10029 None The activation of the CLSID {659CDEA7-489E-11D9-A9CD-000D56965251} timed out waiting for the service BITS to stop. Error 11/25/2025 2:17:47 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 2:17:46 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 2:14:29 AM Microsoft-Windows-DistributedCOM 10010 None The server microsoft.windowscommunicationsapps_16005.14326.22342.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout. Information 11/25/2025 2:07:38 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 11/25/2025 2:07:06 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 2:07:06 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 2:05:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 2:02:12 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 2:01:50 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 2:01:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 1:59:37 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 1:57:15 AM Microsoft-Windows-DistributedCOM 10010 None The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with DCOM within the required timeout. Error 11/25/2025 1:57:04 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 1:54:38 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 1:54:23 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service TrustedInstaller with arguments ""Unavailable"" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED}" Error 11/25/2025 1:54:22 AM Service Control Manager 7000 None "The Windows Modules Installer service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 1:54:22 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Modules Installer service to connect. Error 11/25/2025 1:54:17 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 1:54:17 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/25/2025 1:48:30 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 1:46:07 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 1:43:49 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 1:42:02 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 1:41:33 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 1:37:56 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 1:31:22 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 1:31:22 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 1:31:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Error 11/25/2025 1:30:37 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 1:30:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 1:29:11 AM Microsoft-Windows-DistributedCOM 10010 None The server {0823B6F8-F499-4D5E-B885-EA9CB4F43B24} did not register with DCOM within the required timeout. Error 11/25/2025 1:28:42 AM Microsoft-Windows-DistributedCOM 10010 None The server {659CDEA7-489E-11D9-A9CD-000D56965251} did not register with DCOM within the required timeout. Information 11/25/2025 1:27:05 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/25/2025 1:23:21 AM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/25/2025 1:21:41 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/25/2025 1:21:40 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 1:21:40 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/25/2025 1:20:51 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 1:20:50 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 1:20:20 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/25/2025 1:20:19 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 1:20:15 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/25/2025 1:19:38 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 1:19:37 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/25/2025 1:10:57 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 1:04:47 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 1:02:49 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 1:02:49 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 12:58:49 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 12:58:49 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 12:54:42 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 12:46:20 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 12:46:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/25/2025 12:44:32 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 12:34:15 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 12:34:14 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/25/2025 12:20:36 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 11/25/2025 12:18:02 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/25/2025 12:17:28 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/25/2025 12:17:28 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/25/2025 12:05:16 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:58:04 PM Service Control Manager 7031 None The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Error 11/24/2025 11:58:02 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:58:01 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 11:55:22 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.4239_neutral_neutral_cw5n1h2txyewy!Windows.Networking.BackgroundTransfer.Internal.NetworkChangeTask.ClassId.1 did not register with DCOM within the required timeout. Error 11/24/2025 11:49:43 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:49:42 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 11:43:22 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:43:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 11:37:09 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:34:45 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 11:34:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:33:20 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:33:18 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 11:31:18 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:27:20 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 11:26:25 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:26:25 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 11:25:15 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/24/2025 11:21:47 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service TrustedInstaller with arguments ""Unavailable"" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED}" Error 11/24/2025 11:21:47 PM Service Control Manager 7000 None "The Windows Modules Installer service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:21:46 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Modules Installer service to connect. Error 11/24/2025 11:21:36 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:21:36 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 11:17:06 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:14:47 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:14:47 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 11:14:30 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:14:30 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 11:10:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Warning 11/24/2025 11:09:35 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/24/2025 11:09:35 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/24/2025 11:09:35 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/24/2025 11:09:35 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Error 11/24/2025 11:02:57 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:01:32 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service edgeupdate with arguments ""/comsvc"" in order to run the server: {CECDDD22-2E72-4832-9606-A9B0E5E344B2}" Error 11/24/2025 11:01:32 PM Service Control Manager 7000 None "The Microsoft Edge Update Service (edgeupdate) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:01:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Edge Update Service (edgeupdate) service to connect. Error 11/24/2025 10:53:27 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 10:53:27 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 10:51:12 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 10:39:44 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 10:30:17 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 10:30:16 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 10:19:52 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXf8r3d8cn5hd71h9jyzah6ak9f3shj2d2.mca did not register with DCOM within the required timeout. Error 11/24/2025 10:19:13 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 10:19:13 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 10:15:35 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 10:14:14 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 10:14:14 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 10:09:30 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 10:05:03 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 10:05:02 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 9:56:02 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:56:01 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 9:44:39 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:44:38 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 9:43:38 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:43:37 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 9:39:22 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/24/2025 9:39:21 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:39:20 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/24/2025 9:37:39 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 9:34:19 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/24/2025 9:34:18 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:34:17 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/24/2025 9:31:23 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 9:25:22 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 11/24/2025 9:25:22 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:25:21 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/24/2025 9:17:59 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/24/2025 8:56:34 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 8:54:39 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 8:54:38 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 8:49:30 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 8:49:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 8:42:53 PM Service Control Manager 7031 None The Microsoft Defender Antivirus Network Inspection Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Error 11/24/2025 8:41:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 8:38:46 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 8:36:36 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 8:36:36 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 8:34:46 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 8:28:15 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 8:28:14 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 8:27:23 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 8:27:20 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 8:08:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 8:04:43 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 7:53:39 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 7:53:37 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 7:53:26 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 7:53:25 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 7:48:29 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 7:48:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 7:44:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 7:43:27 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 7:43:26 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 7:43:22 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 7:39:09 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 7:39:00 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/24/2025 7:36:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 7:32:42 PM Microsoft-Windows-DistributedCOM 10010 None The server {544C4C52-DE0B-4D14-9510-21745381D5CA} did not register with DCOM within the required timeout. Error 11/24/2025 7:18:59 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 7:13:49 PM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 7:11:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 7:08:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/24/2025 7:07:27 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 7:05:17 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 7:05:16 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 7:04:56 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 7:04:22 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 7:04:22 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 11/24/2025 7:03:29 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/24/2025 7:00:57 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 6:56:53 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 6:56:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 6:49:40 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/24/2025 6:48:56 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 6:41:06 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 6:41:06 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 6:36:56 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 6:36:13 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 6:36:12 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 6:31:12 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 6:31:11 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 6:30:20 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 6:30:19 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 6:24:21 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 6:09:53 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 5:50:43 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 5:50:43 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 5:44:58 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 5:35:26 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 5:35:25 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 5:35:10 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 5:30:28 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 5:30:27 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 5:26:15 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 5:23:55 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 5:17:43 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 5:11:00 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:59:03 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 4:56:47 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:56:46 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 4:51:06 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:50:08 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 4:46:00 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:45:59 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 4:43:01 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:30:43 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:30:31 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:30:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 4:28:53 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:28:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 4:28:12 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:28:12 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 4:24:27 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:19:24 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:19:24 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 4:14:02 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:11:51 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:07:56 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:05:09 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:05:08 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 4:04:19 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:04:19 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 4:01:35 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:00:20 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:00:19 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 3:52:51 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 3:52:50 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 3:49:43 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 3:49:42 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 3:48:47 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 3:48:46 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 3:44:54 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 3:44:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 3:43:35 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/24/2025 3:43:34 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 3:43:33 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/24/2025 3:41:37 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 3:40:35 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 3:38:17 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 3:36:45 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 3:36:42 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 3:35:51 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 3:33:35 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 3:32:06 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/24/2025 3:32:05 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 3:32:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/24/2025 3:26:23 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 3:24:56 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 3:24:55 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 3:20:35 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 3:18:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 3:16:10 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/24/2025 3:13:20 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/24/2025 3:13:19 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 11/24/2025 3:10:21 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:59:30 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:53:16 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:50:58 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:50:57 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 2:47:07 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:45:30 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:45:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 2:44:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:41:40 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:41:40 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 2:38:37 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:36:53 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:36:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 2:28:04 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:28:03 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 2:26:37 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:19:38 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:19:36 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 2:16:29 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/24/2025 2:15:50 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 11/24/2025 2:10:35 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/24/2025 2:08:51 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/24/2025 1:58:41 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 1:52:24 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 1:45:01 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 1:45:01 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 1:42:13 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 1:30:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 1:26:11 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 1:17:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {F4DF18B4-A2CF-4B0A-8D62-954CD6AD2E33} did not register with DCOM within the required timeout. Error 11/24/2025 1:17:24 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 1:15:10 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 1:13:45 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 1:01:14 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 11/24/2025 12:50:14 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 12:50:14 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 12:45:08 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 12:45:07 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 12:40:47 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 12:38:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 12:26:25 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 12:10:07 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 12:10:06 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 12:05:16 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 12:05:15 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 12:00:04 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Information 11/24/2025 12:00:00 PM EventLog 6013 None The system uptime is 564685 seconds. Information 11/24/2025 11:59:58 AM EventLog 6013 None The system uptime is 564683 seconds. Error 11/24/2025 11:50:49 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:50:03 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 11:50:02 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 11:44:33 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:42:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:30:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 11:16:55 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 11:06:37 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/24/2025 11:05:08 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 11/24/2025 11:05:04 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 11/24/2025 11:05:04 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 11/24/2025 10:51:39 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 10:51:39 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 10:50:39 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 10:40:21 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 10:23:50 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 10:12:30 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 10:00:00 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Information 11/24/2025 9:57:17 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/24/2025 9:51:33 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:51:33 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 9:47:48 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:47:48 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 9:47:04 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:47:04 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 9:38:02 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:38:02 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 9:33:19 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:33:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 9:27:19 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 9:27:19 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 9:02:13 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 9:00:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 8:47:57 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 8:36:21 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 8:34:04 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 8:27:54 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 8:15:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 7:41:40 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 7:31:26 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 7:30:39 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 7:19:08 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.YourPhone_1.25072.79.0_x64__8wekyb3d8bbwe!App.AppXn958k7nsj8mxxmsepqdam8xk948t30sc.mca did not register with DCOM within the required timeout. Error 11/24/2025 7:11:19 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 11/24/2025 7:08:07 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 7:08:06 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 6:53:24 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 6:51:59 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 6:49:58 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 6:49:57 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 6:48:27 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 6:48:27 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 6:39:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 6:32:00 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 6:26:17 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 6:23:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 5:56:45 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 5:45:10 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 5:45:09 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 5:27:38 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 5:27:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 5:26:47 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 5:22:36 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 5:22:35 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 5:12:43 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 5:02:14 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:56:05 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:53:53 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:43:41 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:43:41 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 4:40:28 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:40:28 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/24/2025 4:37:28 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 4:34:08 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:34:07 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/24/2025 4:33:30 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 4:28:26 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:28:26 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 4:25:34 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:25:34 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/24/2025 4:25:27 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 4:25:09 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:25:08 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 4:15:41 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:15:40 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/24/2025 4:10:54 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 4:10:46 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/24/2025 3:58:02 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 3:51:02 AM Microsoft-Windows-DistributedCOM 10010 None The server MicrosoftWindows.Client.CBS_1000.19062.1000.0_x64__cw5n1h2txyewy!Global.Accounts.AppXczw5m0gs1v24mkf1zqkkpebvayhcn73d.mca did not register with DCOM within the required timeout. Error 11/24/2025 3:31:44 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 3:31:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 2:47:52 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:45:39 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:44:04 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:44:04 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 2:43:25 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:43:25 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 2:38:23 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:38:23 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 2:35:23 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:33:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/24/2025 2:33:43 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:33:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 2:33:14 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 2:28:42 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:28:41 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 2:07:17 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 2:07:16 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/24/2025 2:01:58 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 1:59:50 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 1:51:25 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 1:51:24 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 1:49:55 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 1:49:55 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 1:46:33 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 1:25:11 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 1:25:11 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/24/2025 1:17:28 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Error 11/24/2025 1:16:49 AM Microsoft-Windows-DistributedCOM 10010 None The server Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager did not register with DCOM within the required timeout. Error 11/24/2025 1:16:12 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 1:16:12 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/24/2025 1:14:46 AM Microsoft-Windows-DistributedCOM 10010 None The server Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager did not register with DCOM within the required timeout. Error 11/24/2025 1:13:33 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service LxpSvc with arguments ""Unavailable"" in order to run the server: {D0582E3B-3126-4CAA-9155-AC37C912A489}" Error 11/24/2025 1:13:33 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Language Experience Service service to connect. Error 11/24/2025 1:12:44 AM Microsoft-Windows-DistributedCOM 10010 None The server Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager did not register with DCOM within the required timeout. Information 11/24/2025 1:06:30 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/24/2025 1:05:01 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/24/2025 1:05:01 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 1:05:00 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Error 11/24/2025 12:59:41 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/24/2025 12:59:41 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 12:59:41 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Information 11/24/2025 12:51:08 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/24/2025 12:49:42 AM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 12:49:41 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/24/2025 12:13:41 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/24/2025 12:10:48 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/24/2025 12:10:48 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/24/2025 12:09:45 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/24/2025 12:03:20 AM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/23/2025 11:59:32 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/23/2025 11:50:31 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 11/23/2025 11:50:31 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:50:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/23/2025 11:34:34 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:34:34 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 11:31:39 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/23/2025 11:31:39 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:31:38 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/23/2025 11:25:54 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Error 11/23/2025 11:24:53 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:24:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 11:24:36 PM Microsoft-Windows-DistributedCOM 10010 None The server {0823B6F8-F499-4D5E-B885-EA9CB4F43B24} did not register with DCOM within the required timeout. Error 11/23/2025 11:24:13 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:24:13 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 11:22:27 PM Microsoft-Windows-DistributedCOM 10010 None The server {0823B6F8-F499-4D5E-B885-EA9CB4F43B24} did not register with DCOM within the required timeout. Error 11/23/2025 11:19:26 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:19:26 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 11:14:52 PM Microsoft-Windows-DistributedCOM 10010 None The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. Warning 11/23/2025 11:09:37 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/23/2025 11:09:37 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/23/2025 11:09:37 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/23/2025 11:09:37 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 11/23/2025 11:03:15 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:03:14 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 9:31:25 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 9:31:24 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 8:30:59 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.Windows.Search_1.14.18.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. Error 11/23/2025 7:17:51 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/23/2025 7:17:51 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 7:17:51 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/23/2025 6:15:20 PM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Error 11/23/2025 6:08:16 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 6:08:16 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/23/2025 6:07:41 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 6:07:41 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 6:07:41 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 6:07:41 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/23/2025 6:02:42 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 6:02:42 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 6:02:42 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 6:02:42 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/23/2025 6:01:53 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 6:01:53 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 5:56:52 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 5:56:52 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 5:17:05 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 5:17:05 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/23/2025 3:44:58 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/23/2025 3:33:10 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 3:33:10 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/23/2025 3:02:28 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 3:02:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 2:57:25 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:57:25 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 2:56:51 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:56:51 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 2:51:52 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:51:52 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 2:51:10 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:51:10 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 2:46:04 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:46:04 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 2:26:47 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:26:47 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/23/2025 2:06:37 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/23/2025 2:03:48 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/23/2025 2:00:40 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:00:40 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 1:11:57 PM Microsoft-Windows-DistributedCOM 10010 None The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout. Error 11/23/2025 12:51:14 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 12:51:14 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 12:44:58 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 12:44:58 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/23/2025 12:00:01 PM EventLog 6013 None The system uptime is 478286 seconds. Information 11/23/2025 11:59:58 AM EventLog 6013 None The system uptime is 478283 seconds. Error 11/23/2025 11:32:12 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:32:12 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 11:31:36 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:31:35 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 11:26:36 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 11:26:36 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 10:57:06 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 10:57:05 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/23/2025 8:38:17 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/23/2025 8:38:17 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 8:38:17 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Information 11/23/2025 8:32:26 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\microsoft.windows.search_cw5n1h2txyewy\AC\GEH\POF.dat was cleared updating 1 keys and creating 1 modified pages. Error 11/23/2025 8:31:43 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 8:31:43 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 8:26:34 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 8:26:34 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 7:22:03 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 7:22:03 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/23/2025 6:38:48 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/23/2025 6:10:50 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 6:10:48 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 6:10:46 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 6:10:46 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/23/2025 5:59:07 AM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Error 11/23/2025 5:46:50 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 5:46:49 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 5:30:17 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager" Error 11/23/2025 5:30:16 AM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 5:30:15 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/23/2025 5:29:12 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 5:29:12 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/23/2025 5:23:38 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 5:23:37 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/23/2025 2:56:46 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:56:46 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/23/2025 2:18:12 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:18:11 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/23/2025 2:10:38 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 2:10:38 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 1:26:08 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 1:26:08 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/23/2025 1:12:05 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/23/2025 1:12:05 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 11/23/2025 1:00:53 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/23/2025 12:58:19 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/22/2025 11:19:32 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 11:19:31 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Warning 11/22/2025 11:09:38 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 11/22/2025 11:09:38 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 11/22/2025 11:09:38 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 11/22/2025 11:09:38 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Information 11/22/2025 9:32:39 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/22/2025 9:10:24 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 11/22/2025 9:10:24 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 9:10:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Error 11/22/2025 8:26:23 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 8:26:23 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 7:45:51 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 7:45:51 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 6:02:36 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 6:02:35 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/22/2025 6:01:46 PM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Information 11/22/2025 5:49:31 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 11/22/2025 5:49:31 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 11/22/2025 5:49:31 PM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 11/22/2025 5:32:37 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 5:32:37 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/22/2025 5:32:03 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 5:32:03 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/22/2025 5:26:55 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 5:26:55 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/22/2025 5:12:29 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 5:12:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 4:50:44 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 4:50:44 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 4:45:41 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 4:45:41 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 4:04:49 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 4:04:49 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/22/2025 4:04:28 PM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service camsvc with arguments ""Unavailable"" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess" Error 11/22/2025 4:04:28 PM Service Control Manager 7000 None "The Capability Access Manager Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 4:04:28 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Capability Access Manager Service service to connect. Information 11/22/2025 3:29:05 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Settings\settings.dat was cleared updating 5 keys and creating 1 modified pages. Error 11/22/2025 3:23:49 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 3:23:49 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 3:11:15 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 3:11:15 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/22/2025 2:06:02 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 2:06:02 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/22/2025 2:05:23 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/22/2025 2:02:28 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/22/2025 1:15:29 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 1:15:29 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 11/22/2025 12:26:31 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/22/2025 12:00:00 PM EventLog 6013 None The system uptime is 391885 seconds. Information 11/22/2025 11:59:58 AM EventLog 6013 None The system uptime is 391884 seconds. Information 11/22/2025 11:37:38 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 11/22/2025 11:37:34 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 11/22/2025 11:37:34 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Error 11/22/2025 8:26:06 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 8:26:06 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 7:26:11 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 7:26:11 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 6:07:03 AM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Error 11/22/2025 5:51:35 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 5:51:34 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 5:50:59 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 5:50:59 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Error 11/22/2025 5:45:56 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 5:45:56 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/22/2025 3:20:23 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Warning 11/22/2025 1:09:13 AM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Error 11/22/2025 1:02:24 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. Error 11/22/2025 12:56:11 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Information 11/22/2025 12:54:46 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/22/2025 12:49:18 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/22/2025 12:45:52 AM Microsoft-Windows-DistributedCOM 10005 None "DCOM got error ""1053"" attempting to start the service BITS with arguments ""Unavailable"" in order to run the server: {659CDEA7-489E-11D9-A9CD-000D56965251}" Error 11/22/2025 12:45:52 AM Service Control Manager 7000 None "The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/22/2025 12:45:51 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Background Intelligent Transfer Service service to connect. Information 11/22/2025 12:27:43 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/22/2025 12:20:57 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Error 11/21/2025 11:16:37 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/21/2025 11:16:37 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Warning 11/21/2025 11:09:40 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/21/2025 11:09:40 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/21/2025 11:09:40 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/21/2025 11:09:40 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 11/21/2025 6:45:18 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/21/2025 6:45:18 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Information 11/21/2025 6:14:14 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/21/2025 6:05:26 PM Microsoft-Windows-DistributedCOM 10010 None The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. Error 11/21/2025 5:59:07 PM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/21/2025 5:59:07 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Error 11/21/2025 5:46:47 PM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/21/2025 4:38:35 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/21/2025 4:38:35 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/21/2025 2:02:17 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/21/2025 1:58:21 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/21/2025 12:00:00 PM EventLog 6013 None The system uptime is 305485 seconds. Information 11/21/2025 11:59:59 AM EventLog 6013 None The system uptime is 305484 seconds. Error 11/21/2025 11:26:30 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/21/2025 11:23:02 AM Microsoft-Windows-DistributedCOM 10010 None The server Microsoft.AAD.BrokerPlugin_1000.19041.4239.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. Error 11/21/2025 9:25:26 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/21/2025 9:25:26 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/21/2025 9:08:05 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Error 11/21/2025 8:32:46 AM Service Control Manager 7000 None "The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/21/2025 8:32:45 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. Error 11/21/2025 6:01:09 AM Service Control Manager 7000 None "The Client License Service (ClipSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/21/2025 6:01:09 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Client License Service (ClipSVC) service to connect. Information 11/21/2025 5:55:32 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.YourPhone_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\d4be7e4a3deb5b23_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Warning 11/21/2025 2:18:39 AM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 11/21/2025 2:18:36 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat was cleared updating 2 keys and creating 1 modified pages. Information 11/21/2025 12:50:42 AM Microsoft-Windows-Kernel-General 15 (10) Hive \??\C:\WINDOWS\System32\config\COMPONENTS was reorganized with a starting size of 65269760 bytes and an ending size of 43933696 bytes. Error 11/21/2025 12:12:13 AM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/21/2025 12:12:13 AM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/21/2025 12:01:57 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/20/2025 11:35:03 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Warning 11/20/2025 11:09:42 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/20/2025 11:09:42 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/20/2025 11:09:42 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/20/2025 11:09:42 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Error 11/20/2025 10:45:42 PM Service Control Manager 7000 None "The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/20/2025 10:45:42 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. Error 11/20/2025 3:35:55 PM Service Control Manager 7000 None "The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion." Error 11/20/2025 3:35:54 PM Service Control Manager 7009 None A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. Information 11/20/2025 2:55:45 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/20/2025 2:00:11 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/20/2025 1:57:57 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/20/2025 12:00:00 PM EventLog 6013 None The system uptime is 219086 seconds. Information 11/20/2025 11:59:58 AM EventLog 6013 None The system uptime is 219084 seconds. Information 11/20/2025 11:43:11 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\c75fb7e1f4b8ebe1_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/20/2025 11:43:09 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 5 keys and creating 1 modified pages. Information 11/20/2025 10:35:51 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 14 keys and creating 3 modified pages. Information 11/20/2025 9:28:33 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.Search_cw5n1h2txyewy\Settings\settings.dat was cleared updating 36 keys and creating 7 modified pages. Information 11/20/2025 5:49:36 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/20/2025 4:32:04 AM NETwNe64 5010 None "The description for Event ID 5010 from source NETwNe64 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\NDMP3 Intel(R) Centrino(R) Wireless-N 2230 #2 The specified resource type cannot be found in the image file " Information 11/19/2025 11:20:42 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.353.0) - Current Channel (Broad) Information 11/19/2025 11:19:11 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.353.0) - Current Channel (Broad) Information 11/19/2025 11:19:11 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Warning 11/19/2025 11:11:50 PM Tcpip 4205 None Autoconfigured route limit has been reached. No further autoconfigured routes will be added until the interface is reconnected. Warning 11/19/2025 11:09:44 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 11/19/2025 11:09:44 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 11/19/2025 11:09:44 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 11/19/2025 11:09:44 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Information 11/19/2025 8:46:07 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.350.0) - Current Channel (Broad) Information 11/19/2025 8:45:12 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.350.0) - Current Channel (Broad) Information 11/19/2025 8:45:08 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/19/2025 8:43:28 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/19/2025 7:49:07 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/19/2025 7:47:01 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/19/2025 7:44:05 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/19/2025 7:41:51 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/19/2025 1:59:45 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/19/2025 1:57:39 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/19/2025 12:00:00 PM EventLog 6013 None The system uptime is 132686 seconds. Information 11/19/2025 11:59:58 AM EventLog 6013 None The system uptime is 132684 seconds. Information 11/19/2025 11:37:20 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/19/2025 8:56:03 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRD29V9-MICROSOFT.MICROSOFTOFFICEHUB Information 11/19/2025 8:56:02 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRD29V9-MICROSOFT.MICROSOFTOFFICEHUB Information 11/19/2025 8:55:59 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.MicrosoftOfficeHub_19.2511.46031.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/19/2025 8:55:07 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE Information 11/19/2025 8:55:04 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE Information 11/19/2025 8:55:01 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.WindowsStore_22510.1401.2.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/19/2025 8:54:46 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/19/2025 8:54:46 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/19/2025 2:31:12 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/19/2025 1:09:21 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/19/2025 1:09:21 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/19/2025 12:56:59 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\microsoft.windowscommunicationsapps_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 27 keys and creating 3 modified pages. Information 11/18/2025 11:19:44 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.331.0) - Current Channel (Broad) Information 11/18/2025 11:19:25 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.331.0) - Current Channel (Broad) Information 11/18/2025 11:19:25 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/18/2025 11:12:37 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/18/2025 11:10:33 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Warning 11/18/2025 11:09:46 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 11/18/2025 11:09:46 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 11/18/2025 11:09:46 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Warning 11/18/2025 11:09:46 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86397 seconds since the last report. Information 11/18/2025 9:44:59 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.328.0) - Current Channel (Broad) Information 11/18/2025 9:44:44 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.328.0) - Current Channel (Broad) Information 11/18/2025 9:44:44 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/18/2025 9:44:36 PM Microsoft-Windows-Kernel-General 15 (10) Hive \SystemRoot\System32\config\DRIVERS was reorganized with a starting size of 6795264 bytes and an ending size of 6791168 bytes. Information 11/18/2025 9:00:35 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/18/2025 8:58:23 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/18/2025 7:49:08 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/18/2025 7:47:02 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/18/2025 5:53:39 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.YourPhone_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 46 keys and creating 5 modified pages. Information 11/18/2025 5:25:04 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/18/2025 1:59:39 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/18/2025 1:57:34 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/18/2025 12:01:02 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/18/2025 12:00:00 PM EventLog 6013 None The system uptime is 46285 seconds. Information 11/18/2025 11:59:59 AM EventLog 6013 None The system uptime is 46284 seconds. Information 11/18/2025 11:58:52 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/18/2025 8:18:56 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/18/2025 5:08:40 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\55c495c91f34bcc0_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/18/2025 12:21:04 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/18/2025 12:04:00 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/17/2025 11:46:56 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/17/2025 11:29:52 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/17/2025 11:18:58 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-Provisioning-Sequence.dat was cleared updating 0 keys and creating 0 modified pages. Error 11/17/2025 11:13:42 PM Microsoft-Windows-TPM-WMI 1801 None "Secure Boot CA/keys need to be updated. This device signature information is included here. DeviceAttributes: BaseBoardManufacturer:INTEL Corporation;FirmwareManufacturer:American Megatrends Inc.;FirmwareVersion:5.6.5;OEMModelNumber:To be filled by O.E.M.;OEMModelBaseBoard:CRESCENTBAY;OEMModelSystemFamily:To be filled by O.E.M.;OEMManufacturerName:To be filled by O.E.M.;OEMModelSKU:To be filled by O.E.M.;OSArchitecture:amd64; BucketId: 3172bfdf51002a90ec09ce6a4c3dd16df4a8a200aa84b1d0136a4916f76764e2 BucketConfidenceLevel: UpdateType: 0 HResult: The operation completed successfully." Information 11/17/2025 11:12:48 PM Microsoft-Windows-Time-Service 35 None The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123) with reference id 494637363. Current local stratum number is 4. Information 11/17/2025 11:12:48 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Warning 11/17/2025 11:10:48 PM 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." Warning 11/17/2025 11:10:48 PM 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.WscBrokerManager 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." Warning 11/17/2025 11:10:48 PM 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.SecurityAppBroker 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." Information 11/17/2025 11:10:47 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Warning 11/17/2025 11:09:48 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/17/2025 11:09:48 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/17/2025 11:09:48 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/17/2025 11:09:48 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Information 11/17/2025 11:09:06 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 2025-11 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5072653) Error 11/17/2025 11:09:01 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/17/2025 11:09:01 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/17/2025 11:09:01 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/17/2025 11:09:01 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/17/2025 11:09:01 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/17/2025 11:09:01 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/17/2025 11:09:01 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/17/2025 11:09:01 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Warning 11/17/2025 11:08:55 PM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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 11/17/2025 11:08:55 PM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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." Information 11/17/2025 11:08:49 PM Microsoft-Windows-Winlogon 7001 (1101) User Logon Notification for Customer Experience Improvement Program Information 11/17/2025 11:08:49 PM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Information 11/17/2025 11:08:46 PM Service Control Manager 7026 None "The following boot-start or system-start driver(s) did not load: dam" Warning 11/17/2025 11:08:45 PM Microsoft-Windows-DNS-Client 1014 (1014) Name resolution for the name hb-a.services.vnc.com timed out after none of the configured DNS servers responded. Error 11/17/2025 11:08:44 PM Service Control Manager 7034 None The MediaMTX service terminated unexpectedly. It has done this 1 time(s). Error 11/17/2025 11:08:43 PM Service Control Manager 7024 None "The MediaMTX service terminated with the following service-specific error: The system cannot find the path specified." Error 11/17/2025 11:08:43 PM Tcpip 4199 None The system detected an address conflict for IP address :: with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. Information 11/17/2025 11:08:42 PM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection #2 Network link has been established at 1Gbps full duplex. " Information 11/17/2025 11:08:42 PM Microsoft-Windows-WLAN-AutoConfig 4000 None "WLAN AutoConfig service has successfully started. " Information 11/17/2025 11:08:42 PM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection Network link has been established at 1Gbps full duplex. " Information 11/17/2025 11:08:40 PM Microsoft-Windows-DHCPv6-Client 51046 Service State Event DHCPv6 client service is started Information 11/17/2025 11:08:40 PM Microsoft-Windows-Dhcp-Client 50103 Service State Event DHCPv4 client registered for shutdown notification Information 11/17/2025 11:08:40 PM Microsoft-Windows-Dhcp-Client 50036 Service State Event DHCPv4 client service is started Information 11/17/2025 11:08:40 PM Microsoft-Windows-FilterManager 6 None File System Filter 'bindflt' (10.0, ‎2091‎-‎04‎-‎15T15:55:03.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:40 PM Microsoft-Windows-FilterManager 6 None File System Filter 'storqosflt' (10.0, ‎2038‎-‎12‎-‎03T01:18:20.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:40 PM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:40 PM Microsoft-Windows-FilterManager 1 None File System Filter 'CldFlt' (Version 10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) unloaded successfully. Information 11/17/2025 11:08:40 PM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:40 PM Microsoft-Windows-FilterManager 6 None File System Filter 'luafv' (10.0, ‎1996‎-‎01‎-‎27T04:16:28.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:40 PM Microsoft-Windows-FilterManager 6 None File System Filter 'wcifs' (10.0, ‎2043‎-‎11‎-‎04T03:04:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:39 PM Microsoft-Windows-Directory-Services-SAM 16983 None "The security account manager is now logging periodic summary events for remote clients that call legacy password change or set RPC methods. For more information please see https://go.microsoft.com/fwlink/?linkid=2150956. " Information 11/17/2025 11:08:39 PM Microsoft-Windows-Directory-Services-SAM 16977 None "The domain is configured with the following minimum password length-related settings. MinimumPasswordLength: 0 RelaxMinimumPasswordLengthLimits: 0 MinimumPasswordLengthAudit: -1 For more information see https://go.microsoft.com/fwlink/?LinkId=2097191. " Information 11/17/2025 11:08:39 PM Microsoft-Windows-Directory-Services-SAM 16962 None "Remote calls to the SAM database are being restricted using the default security descriptor: O:SYG:SYD:(A;;RC;;;BA). For more information please see http://go.microsoft.com/fwlink/?LinkId=787651." Information 11/17/2025 11:08:39 PM Microsoft-Windows-Wininit 14 None Credential Guard configuration: 0x0, 0 Warning 11/17/2025 11:08:39 PM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 11/17/2025 11:08:39 PM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Warning 11/17/2025 11:08:38 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Warning 11/17/2025 11:08:38 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Information 11/17/2025 11:08:37 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/17/2025 11:08:37 PM NETwNe64 7036 None The \Device\NDMP3 service entered the Intel(R) Centrino(R) Wireless-N 2230 #2 state. Information 11/17/2025 11:08:36 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 3 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/17/2025 11:08:36 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 1 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/17/2025 11:08:36 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 2 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/17/2025 11:08:36 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 0 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/17/2025 11:08:36 PM Microsoft-Windows-Ntfs 98 None Volume \\?\Volume{df4bd8a4-f614-4d33-bbb6-6885459a0935} (\Device\HarddiskVolume1) is healthy. No action is needed. Information 11/17/2025 11:08:36 PM Microsoft-Windows-Ntfs 98 None Volume D: (\Device\HarddiskVolume5) is healthy. No action is needed. Information 11/17/2025 11:08:36 PM Microsoft-Windows-Kernel-Power 172 (203) Connectivity state in standby: Disconnected, Reason: NIC compliance Information 11/17/2025 11:08:36 PM Microsoft-Windows-FilterManager 6 None File System Filter 'npsvctrig' (10.0, ‎2025‎-‎01‎-‎05T18:41:12.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:35 PM Microsoft-Windows-FilterManager 6 None File System Filter 'UCPD' (10.0, ‎2006‎-‎08‎-‎28T03:56:22.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:35 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileCrypt' (10.0, ‎2002‎-‎03‎-‎01T03:12:42.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:35 PM Microsoft-Windows-Ntfs 98 None Volume C: (\Device\HarddiskVolume4) is healthy. No action is needed. Information 11/17/2025 11:08:35 PM Microsoft-Windows-FilterManager 6 None File System Filter 'WdFilter' (10.0, ‎2029‎-‎01‎-‎09T21:59:29.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:35 PM Microsoft-Windows-FilterManager 6 None File System Filter 'Wof' (10.0, ‎2090‎-‎03‎-‎16T10:56:17.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:35 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (10.0, ‎2062‎-‎12‎-‎22T21:21:06.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 11:08:35 PM Microsoft-Windows-HAL 16 None The iommu fault reporting has been initialized. Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-General 20 (6) "The leap second configuration has been updated. Reason: Leap second data initialized from registry during boot Leap seconds enabled: true New leap second count: 0 Old leap second count: 0" Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-Boot 30 (21) The firmware reported boot metrics. Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-Boot 32 (58) The bootmgr spent 0 ms waiting for user input. Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-Boot 18 (57) There are 0x1 boot options on this system. Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-Boot 27 (33) The boot type was 0x0. Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-Boot 25 (32) The boot menu policy was 0x1. Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-Boot 238 (101) EFI time zone bias: 2047. Daylight flags: 0 Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-Boot 20 (31) The last shutdown's success status was true. The last boot's success status was true. Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-Boot 153 (62) Virtualization-based security (policies: 0) is disabled. Information 11/17/2025 11:08:34 PM Microsoft-Windows-Kernel-General 12 (1) The operating system started at system time ‎2025‎-‎11‎-‎18T07:08:34.500000000Z. Information 11/17/2025 11:08:26 PM Microsoft-Windows-Kernel-General 13 (2) The operating system is shutting down at system time ‎2025‎-‎11‎-‎18T07:08:26.523453200Z. Information 11/17/2025 11:08:26 PM Microsoft-Windows-Kernel-Power 109 (103) "The kernel power manager has initiated a shutdown transition. Shutdown Reason: Kernel API" Information 11/17/2025 11:08:22 PM Microsoft-Windows-WLAN-AutoConfig 4001 None "WLAN AutoConfig service has successfully stopped. " Information 11/17/2025 11:08:40 PM EventLog 6013 None The system uptime is 6 seconds. Information 11/17/2025 11:08:40 PM EventLog 6005 None The Event log service was started. Information 11/17/2025 11:08:40 PM EventLog 6009 None Microsoft (R) Windows (R) 10.00. 19045 Multiprocessor Free. Information 11/17/2025 11:08:21 PM Microsoft-Windows-Dhcp-Client 50037 Service State Event DHCPv4 client service is stopped. ShutDown Flag value is 1 Information 11/17/2025 11:08:21 PM Microsoft-Windows-Dhcp-Client 50106 Service State Event DHCPv4 is waiting on DHCPv6 service to stop Information 11/17/2025 11:08:21 PM Microsoft-Windows-DHCPv6-Client 51057 Service State Event DHCPv6 client service stop is almost done.DHCP Context Ref count is 1 Information 11/17/2025 11:08:21 PM Microsoft-Windows-DHCPv6-Client 51057 Service State Event DHCPv6 client service stop is almost done.DHCP Context Ref count is 1 Information 11/17/2025 11:08:21 PM Microsoft-Windows-DHCPv6-Client 51047 Service State Event DHCPv6 client service is stopped. ShutDown Flag value is 1 Information 11/17/2025 11:08:21 PM Microsoft-Windows-Dhcp-Client 50105 Service State Event DHCPv4 client ProcessDHCPRequestForever received TERMINATE_EVENT Information 11/17/2025 11:08:21 PM Microsoft-Windows-Dhcp-Client 50104 Service State Event DHCPv4 client received shutdown notification Information 11/17/2025 11:08:21 PM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎18T07:08:21.117759500Z from ‎2025‎-‎11‎-‎18T07:08:21.110793800Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 5488)." Information 11/17/2025 11:08:21 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/17/2025 11:08:21 PM EventLog 6006 None The Event log service was stopped. Information 11/17/2025 11:08:06 PM Microsoft-Windows-Winlogon 7002 (1102) User Logoff Notification for Customer Experience Improvement Program Information 11/17/2025 11:08:01 PM User32 1074 None "The process C:\WINDOWS\system32\svchost.exe (DESKTOP-JGMFQDF) has initiated the restart of computer DESKTOP-JGMFQDF on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Service pack (Planned) Reason Code: 0x80020010 Shutdown Type: restart Comment: " Information 11/17/2025 11:01:08 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/17/2025 10:59:04 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/17/2025 10:46:59 PM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/17/2025 10:46:58 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 2025-11 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5072653) Information 11/17/2025 10:46:56 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Update for Microsoft Defender Antivirus antimalware platform - KB4052623 (Version 4.18.25100.9008) - Current Channel (Broad) Information 11/17/2025 10:46:31 PM Service Control Manager 7045 None "A service was installed in the system. Service Name: KslD Service File Name: system32\drivers\wd\KslD.sys Service Type: kernel mode driver Service Start Type: demand start Service Account: " Information 11/17/2025 10:46:31 PM Microsoft-Windows-FilterManager 6 None File System Filter 'WdFilter' (10.0, ‎2029‎-‎01‎-‎09T21:59:29.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/17/2025 10:46:23 PM Microsoft-Windows-FilterManager 1 None File System Filter 'WdFilter' (Version 10.0, ‎1977‎-‎06‎-‎03T08:32:50.000000000Z) unloaded successfully. Information 11/17/2025 10:45:57 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Update for Microsoft Defender Antivirus antimalware platform - KB4052623 (Version 4.18.25100.9008) - Current Channel (Broad) Information 11/17/2025 10:45:54 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.305.0) - Current Channel (Broad) Information 11/17/2025 10:44:50 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.305.0) - Current Channel (Broad) Information 11/17/2025 10:44:50 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/17/2025 10:44:48 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/17/2025 10:44:48 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/17/2025 8:49:11 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/17/2025 8:46:59 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/17/2025 7:50:42 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/17/2025 7:47:02 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/17/2025 2:07:39 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/17/2025 1:59:34 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/17/2025 1:57:29 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/17/2025 12:00:00 PM EventLog 6013 None The system uptime is 123555 seconds. Information 11/17/2025 11:59:58 AM EventLog 6013 None The system uptime is 123553 seconds. Information 11/17/2025 5:01:31 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/17/2025 1:51:46 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.285.0) - Current Channel (Broad) Information 11/17/2025 1:51:26 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.285.0) - Current Channel (Broad) Information 11/17/2025 1:51:26 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/17/2025 1:45:23 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Information 11/17/2025 1:44:02 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/17/2025 1:43:47 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Information 11/17/2025 1:43:43 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/17/2025 1:43:42 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Warning 11/17/2025 1:41:56 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Warning 11/17/2025 1:41:56 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Warning 11/17/2025 1:41:56 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Warning 11/17/2025 1:41:56 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86401 seconds since the last report. Information 11/17/2025 1:40:53 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/17/2025 12:02:26 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.283.0) - Current Channel (Broad) Information 11/17/2025 12:02:09 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.283.0) - Current Channel (Broad) Information 11/17/2025 12:02:09 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/16/2025 7:55:23 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/16/2025 7:50:41 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/16/2025 7:47:03 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/16/2025 1:59:29 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/16/2025 1:57:23 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/16/2025 12:00:00 PM EventLog 6013 None The system uptime is 37155 seconds. Information 11/16/2025 10:49:15 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/16/2025 3:44:27 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/16/2025 3:42:22 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/16/2025 2:51:40 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/16/2025 2:34:36 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/16/2025 2:17:32 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/16/2025 2:00:28 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/16/2025 1:51:19 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-Provisioning-Sequence.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/16/2025 1:48:51 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.261.0) - Current Channel (Broad) Information 11/16/2025 1:48:38 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.261.0) - Current Channel (Broad) Information 11/16/2025 1:48:38 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Error 11/16/2025 1:45:52 AM Microsoft-Windows-TPM-WMI 1801 None "Secure Boot CA/keys need to be updated. This device signature information is included here. DeviceAttributes: BaseBoardManufacturer:INTEL Corporation;FirmwareManufacturer:American Megatrends Inc.;FirmwareVersion:5.6.5;OEMModelNumber:To be filled by O.E.M.;OEMModelBaseBoard:CRESCENTBAY;OEMModelSystemFamily:To be filled by O.E.M.;OEMManufacturerName:To be filled by O.E.M.;OEMModelSKU:To be filled by O.E.M.;OSArchitecture:amd64; BucketId: 3172bfdf51002a90ec09ce6a4c3dd16df4a8a200aa84b1d0136a4916f76764e2 BucketConfidenceLevel: UpdateType: 0 HResult: The operation completed successfully." Information 11/16/2025 1:43:24 AM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎16T09:43:24.547218800Z from ‎2025‎-‎11‎-‎16T09:43:24.546322400Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 5488)." Information 11/16/2025 1:43:24 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/16/2025 1:43:24 AM Microsoft-Windows-Time-Service 35 None The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123) with reference id 494637363. Current local stratum number is 4. Information 11/16/2025 1:43:24 AM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎16T09:43:24.546322400Z from ‎2025‎-‎11‎-‎16T09:43:21.492818800Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 5488)." Information 11/16/2025 1:43:24 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/16/2025 1:43:07 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Warning 11/16/2025 1:43:05 AM 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." Information 11/16/2025 1:43:05 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Warning 11/16/2025 1:41:55 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/16/2025 1:41:55 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/16/2025 1:41:55 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/16/2025 1:41:55 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Information 11/16/2025 1:41:32 AM Microsoft-Windows-WER-SystemErrorReporting 1018 None The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space. Error 11/16/2025 1:41:22 AM Microsoft-Windows-WER-SystemErrorReporting 1001 None The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x000000000000003f, 0x000000000016c0db, 0x00000000d2b5527d, 0x0000000056fe7307). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0df14058-f790-4ea9-98f4-faef017fcc2d. Information 11/16/2025 1:41:17 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\Settings\settings.dat was cleared updating 3 keys and creating 1 modified pages. Information 11/16/2025 1:41:17 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\microsoft.windows.search_cw5n1h2txyewy\AC\GEH\POF.dat was cleared updating 7 keys and creating 1 modified pages. Error 11/16/2025 1:41:17 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/16/2025 1:41:17 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/16/2025 1:41:17 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/16/2025 1:41:17 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/16/2025 1:41:17 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/16/2025 1:41:17 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/16/2025 1:41:17 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/16/2025 1:41:17 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Warning 11/16/2025 1:41:08 AM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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 11/16/2025 1:41:08 AM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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." Information 11/16/2025 1:41:04 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\AppCompat\Programs\Amcache.hve.tmp was cleared updating 0 keys and creating 0 modified pages. Information 11/16/2025 1:41:03 AM Service Control Manager 7026 None "The following boot-start or system-start driver(s) did not load: dam" Information 11/16/2025 1:41:00 AM Microsoft-Windows-Winlogon 7001 (1101) User Logon Notification for Customer Experience Improvement Program Error 11/16/2025 1:41:00 AM Service Control Manager 7034 None The MediaMTX service terminated unexpectedly. It has done this 1 time(s). Error 11/16/2025 1:41:00 AM Service Control Manager 7024 None "The MediaMTX service terminated with the following service-specific error: The system cannot find the path specified." Information 11/16/2025 1:40:58 AM Microsoft-Windows-WLAN-AutoConfig 4000 None "WLAN AutoConfig service has successfully started. " Information 11/16/2025 1:40:51 AM Microsoft-Windows-DHCPv6-Client 51046 Service State Event DHCPv6 client service is started Information 11/16/2025 1:40:51 AM Microsoft-Windows-Dhcp-Client 50103 Service State Event DHCPv4 client registered for shutdown notification Information 11/16/2025 1:40:51 AM Microsoft-Windows-Dhcp-Client 50036 Service State Event DHCPv4 client service is started Information 11/16/2025 1:40:51 AM Microsoft-Windows-FilterManager 6 None File System Filter 'bindflt' (10.0, ‎2091‎-‎04‎-‎15T15:55:03.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:51 AM Microsoft-Windows-FilterManager 6 None File System Filter 'storqosflt' (10.0, ‎2038‎-‎12‎-‎03T01:18:20.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:51 AM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:51 AM Microsoft-Windows-FilterManager 1 None File System Filter 'CldFlt' (Version 10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) unloaded successfully. Information 11/16/2025 1:40:51 AM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:51 AM Microsoft-Windows-FilterManager 6 None File System Filter 'luafv' (10.0, ‎1996‎-‎01‎-‎27T04:16:28.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:51 AM Microsoft-Windows-FilterManager 6 None File System Filter 'wcifs' (10.0, ‎2043‎-‎11‎-‎04T03:04:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:50 AM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection #2 Network link has been established at 1Gbps full duplex. " Information 11/16/2025 1:40:50 AM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection Network link has been established at 1Gbps full duplex. " Information 11/16/2025 1:40:49 AM Microsoft-Windows-Directory-Services-SAM 16983 None "The security account manager is now logging periodic summary events for remote clients that call legacy password change or set RPC methods. For more information please see https://go.microsoft.com/fwlink/?linkid=2150956. " Information 11/16/2025 1:40:49 AM Microsoft-Windows-Directory-Services-SAM 16977 None "The domain is configured with the following minimum password length-related settings. MinimumPasswordLength: 0 RelaxMinimumPasswordLengthLimits: 0 MinimumPasswordLengthAudit: -1 For more information see https://go.microsoft.com/fwlink/?LinkId=2097191. " Information 11/16/2025 1:40:49 AM Microsoft-Windows-Directory-Services-SAM 16962 None "Remote calls to the SAM database are being restricted using the default security descriptor: O:SYG:SYD:(A;;RC;;;BA). For more information please see http://go.microsoft.com/fwlink/?LinkId=787651." Information 11/16/2025 1:40:49 AM Microsoft-Windows-Wininit 14 None Credential Guard configuration: 0x0, 0 Warning 11/16/2025 1:40:48 AM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 11/16/2025 1:40:48 AM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Information 11/16/2025 1:40:47 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Warning 11/16/2025 1:40:46 AM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Warning 11/16/2025 1:40:46 AM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Information 11/16/2025 1:40:44 AM Microsoft-Windows-Ntfs 98 None Volume \\?\Volume{df4bd8a4-f614-4d33-bbb6-6885459a0935} (\Device\HarddiskVolume1) is healthy. No action is needed. Information 11/16/2025 1:40:44 AM NETwNe64 7036 None The \Device\NDMP4 service entered the Intel(R) Centrino(R) Wireless-N 2230 #2 state. Information 11/16/2025 1:40:44 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 3 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/16/2025 1:40:44 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 1 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/16/2025 1:40:44 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 2 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/16/2025 1:40:44 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 0 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/16/2025 1:40:44 AM Microsoft-Windows-Ntfs 98 None Volume D: (\Device\HarddiskVolume5) is healthy. No action is needed. Information 11/16/2025 1:40:43 AM Microsoft-Windows-Kernel-Power 172 (203) Connectivity state in standby: Disconnected, Reason: NIC compliance Critical 11/16/2025 1:40:43 AM 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. Information 11/16/2025 1:40:43 AM Microsoft-Windows-FilterManager 6 None File System Filter 'npsvctrig' (10.0, ‎2025‎-‎01‎-‎05T18:41:12.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:43 AM Microsoft-Windows-FilterManager 6 None File System Filter 'UCPD' (10.0, ‎2006‎-‎08‎-‎28T03:56:22.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:43 AM Microsoft-Windows-FilterManager 6 None File System Filter 'FileCrypt' (10.0, ‎2002‎-‎03‎-‎01T03:12:42.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:42 AM Microsoft-Windows-Ntfs 98 None Volume C: (\Device\HarddiskVolume4) is healthy. No action is needed. Information 11/16/2025 1:40:42 AM Microsoft-Windows-FilterManager 6 None File System Filter 'WdFilter' (10.0, ‎1977‎-‎06‎-‎03T08:32:50.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:42 AM Microsoft-Windows-FilterManager 6 None File System Filter 'Wof' (10.0, ‎2090‎-‎03‎-‎16T10:56:17.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:42 AM Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (10.0, ‎2062‎-‎12‎-‎22T21:21:06.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/16/2025 1:40:42 AM Microsoft-Windows-HAL 16 None The iommu fault reporting has been initialized. Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-General 20 (6) "The leap second configuration has been updated. Reason: Leap second data initialized from registry during boot Leap seconds enabled: true New leap second count: 0 Old leap second count: 0" Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-Boot 30 (21) The firmware reported boot metrics. Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-Boot 32 (58) The bootmgr spent 0 ms waiting for user input. Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-Boot 18 (57) There are 0x1 boot options on this system. Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-Boot 27 (33) The boot type was 0x0. Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-Boot 25 (32) The boot menu policy was 0x1. Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-Boot 238 (101) EFI time zone bias: 2047. Daylight flags: 0 Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-Boot 20 (31) The last shutdown's success status was false. The last boot's success status was true. Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-Boot 153 (62) Virtualization-based security (policies: 0) is disabled. Information 11/16/2025 1:40:51 AM EventLog 6013 None The system uptime is 9 seconds. Information 11/16/2025 1:40:51 AM EventLog 6005 None The Event log service was started. Information 11/16/2025 1:40:51 AM EventLog 6009 None Microsoft (R) Windows (R) 10.00. 19045 Multiprocessor Free. Error 11/16/2025 1:40:51 AM EventLog 6008 None The previous system shutdown at 5:59:32 PM on ‎11/‎13/‎2025 was unexpected. Information 11/16/2025 1:40:41 AM Microsoft-Windows-Kernel-General 12 (1) The operating system started at system time ‎2025‎-‎11‎-‎16T09:40:41.500000000Z. Information 11/16/2025 1:04:34 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/15/2025 7:49:45 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/15/2025 7:47:28 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/15/2025 7:26:56 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/15/2025 7:24:27 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/15/2025 6:49:25 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/15/2025 6:47:18 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/15/2025 6:14:41 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.254.0) - Current Channel (Broad) Information 11/15/2025 6:11:19 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.254.0) - Current Channel (Broad) Information 11/15/2025 6:11:18 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Warning 11/15/2025 6:00:34 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/15/2025 6:00:34 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/15/2025 6:00:34 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Warning 11/15/2025 6:00:34 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86398 seconds since the last report. Information 11/15/2025 3:58:26 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/15/2025 1:21:28 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/15/2025 1:18:51 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/15/2025 12:46:55 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Settings\settings.dat was cleared updating 5 keys and creating 1 modified pages. Information 11/15/2025 12:00:00 PM EventLog 6013 None The system uptime is 151235 seconds. Information 11/15/2025 11:59:58 AM EventLog 6013 None The system uptime is 151233 seconds. Information 11/15/2025 9:22:53 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/15/2025 9:20:47 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/15/2025 6:52:18 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/15/2025 6:21:29 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.240.0) - Current Channel (Broad) Information 11/15/2025 6:20:34 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.240.0) - Current Channel (Broad) Information 11/15/2025 6:20:34 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/15/2025 3:21:07 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/15/2025 3:18:51 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/15/2025 1:16:35 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9NHT9RB2F4HD-Microsoft.Copilot Information 11/15/2025 1:16:33 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Copilot_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/15/2025 1:16:32 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9NHT9RB2F4HD-Microsoft.Copilot Information 11/15/2025 1:15:31 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/14/2025 7:49:08 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/14/2025 7:47:03 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/14/2025 6:49:16 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/14/2025 6:45:43 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/14/2025 6:11:06 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.230.0) - Current Channel (Broad) Information 11/14/2025 6:10:29 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.230.0) - Current Channel (Broad) Information 11/14/2025 6:10:29 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Warning 11/14/2025 6:00:36 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86396 seconds since the last report. Warning 11/14/2025 6:00:36 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86396 seconds since the last report. Warning 11/14/2025 6:00:36 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86396 seconds since the last report. Warning 11/14/2025 6:00:36 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 86396 seconds since the last report. Information 11/14/2025 5:22:52 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/14/2025 5:18:52 PM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/14/2025 12:00:00 PM EventLog 6013 None The system uptime is 64835 seconds. Information 11/14/2025 11:59:59 AM EventLog 6013 None The system uptime is 64834 seconds. Information 11/14/2025 9:22:46 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/14/2025 9:20:41 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/14/2025 7:31:20 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/14/2025 7:29:07 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/14/2025 7:27:23 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.215.0) - Current Channel (Broad) Information 11/14/2025 7:27:01 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.215.0) - Current Channel (Broad) Information 11/14/2025 7:27:01 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/14/2025 5:30:21 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/14/2025 5:28:16 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/14/2025 4:20:15 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/14/2025 4:18:11 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Warning 11/14/2025 4:14:32 AM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 11/14/2025 3:54:11 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\AppCompat\Programs\Amcache.hve.tmp was cleared updating 0 keys and creating 0 modified pages. Warning 11/14/2025 2:18:13 AM 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 DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) 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." Information 11/14/2025 2:14:30 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy\Settings\settings.dat was cleared updating 10346 keys and creating 325 modified pages. Information 11/13/2025 7:01:54 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/13/2025 6:44:50 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/13/2025 6:27:46 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/13/2025 6:27:46 PM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎14T02:27:46.282054600Z from ‎2025‎-‎11‎-‎14T02:27:46.280941000Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 2916)." Information 11/13/2025 6:27:46 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/13/2025 6:27:46 PM Microsoft-Windows-Time-Service 35 None The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123) with reference id 494637363. Current local stratum number is 4. Information 11/13/2025 6:27:46 PM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎14T02:27:46.280941000Z from ‎2025‎-‎11‎-‎14T02:27:48.139239600Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 2916)." Information 11/13/2025 6:27:46 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/13/2025 6:27:48 PM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Information 11/13/2025 6:18:59 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/13/2025 6:10:55 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.206.0) - Current Channel (Broad) Information 11/13/2025 6:10:39 PM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.206.0) - Current Channel (Broad) Information 11/13/2025 6:10:39 PM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 6:10:25 PM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-Provisioning-Sequence.dat was cleared updating 0 keys and creating 0 modified pages. Warning 11/13/2025 6:05:48 PM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Error 11/13/2025 6:04:33 PM Microsoft-Windows-TPM-WMI 1801 None "Secure Boot CA/keys need to be updated. This device signature information is included here. DeviceAttributes: BaseBoardManufacturer:INTEL Corporation;FirmwareManufacturer:American Megatrends Inc.;FirmwareVersion:5.6.5;OEMModelNumber:To be filled by O.E.M.;OEMModelBaseBoard:CRESCENTBAY;OEMModelSystemFamily:To be filled by O.E.M.;OEMManufacturerName:To be filled by O.E.M.;OEMModelSKU:To be filled by O.E.M.;OSArchitecture:amd64; BucketId: 3172bfdf51002a90ec09ce6a4c3dd16df4a8a200aa84b1d0136a4916f76764e2 BucketConfidenceLevel: UpdateType: 0 HResult: The operation completed successfully." Warning 11/13/2025 6:01:39 PM 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." Warning 11/13/2025 6:01:39 PM 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.WscBrokerManager 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." Warning 11/13/2025 6:01:39 PM 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.SecurityAppBroker 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." Information 11/13/2025 6:01:39 PM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Warning 11/13/2025 6:00:40 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/13/2025 6:00:40 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/13/2025 6:00:40 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/13/2025 6:00:40 PM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Information 11/13/2025 6:00:30 PM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 2025-11 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5071959) Warning 11/13/2025 6:00:12 PM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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 11/13/2025 6:00:12 PM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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." Information 11/13/2025 6:00:07 PM Microsoft-Windows-Winlogon 7001 (1101) User Logon Notification for Customer Experience Improvement Program Information 11/13/2025 6:00:06 PM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Error 11/13/2025 5:59:49 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/13/2025 5:59:49 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/13/2025 5:59:49 PM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Information 11/13/2025 5:59:38 PM Service Control Manager 7026 None "The following boot-start or system-start driver(s) did not load: dam" Error 11/13/2025 5:59:36 PM Service Control Manager 7034 None The MediaMTX service terminated unexpectedly. It has done this 1 time(s). Error 11/13/2025 5:59:35 PM Service Control Manager 7024 None "The MediaMTX service terminated with the following service-specific error: The system cannot find the path specified." Information 11/13/2025 5:59:34 PM Microsoft-Windows-WLAN-AutoConfig 4000 None "WLAN AutoConfig service has successfully started. " Information 11/13/2025 5:59:34 PM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection #2 Network link has been established at 1Gbps full duplex. " Information 11/13/2025 5:59:34 PM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection Network link has been established at 1Gbps full duplex. " Information 11/13/2025 5:59:32 PM Microsoft-Windows-DHCPv6-Client 51046 Service State Event DHCPv6 client service is started Information 11/13/2025 5:59:32 PM Microsoft-Windows-Dhcp-Client 50103 Service State Event DHCPv4 client registered for shutdown notification Information 11/13/2025 5:59:32 PM Microsoft-Windows-Dhcp-Client 50036 Service State Event DHCPv4 client service is started Information 11/13/2025 5:59:32 PM Microsoft-Windows-FilterManager 6 None File System Filter 'bindflt' (10.0, ‎2091‎-‎04‎-‎15T15:55:03.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:32 PM Microsoft-Windows-FilterManager 6 None File System Filter 'storqosflt' (10.0, ‎2038‎-‎12‎-‎03T01:18:20.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:32 PM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:32 PM Microsoft-Windows-FilterManager 1 None File System Filter 'CldFlt' (Version 10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) unloaded successfully. Information 11/13/2025 5:59:32 PM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:32 PM Microsoft-Windows-FilterManager 6 None File System Filter 'luafv' (10.0, ‎1996‎-‎01‎-‎27T04:16:28.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:32 PM Microsoft-Windows-FilterManager 6 None File System Filter 'wcifs' (10.0, ‎2043‎-‎11‎-‎04T03:04:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:31 PM Microsoft-Windows-Directory-Services-SAM 16983 None "The security account manager is now logging periodic summary events for remote clients that call legacy password change or set RPC methods. For more information please see https://go.microsoft.com/fwlink/?linkid=2150956. " Information 11/13/2025 5:59:31 PM Microsoft-Windows-Directory-Services-SAM 16977 None "The domain is configured with the following minimum password length-related settings. MinimumPasswordLength: 0 RelaxMinimumPasswordLengthLimits: 0 MinimumPasswordLengthAudit: -1 For more information see https://go.microsoft.com/fwlink/?LinkId=2097191. " Information 11/13/2025 5:59:31 PM Microsoft-Windows-Directory-Services-SAM 16962 None "Remote calls to the SAM database are being restricted using the default security descriptor: O:SYG:SYD:(A;;RC;;;BA). For more information please see http://go.microsoft.com/fwlink/?LinkId=787651." Information 11/13/2025 5:59:31 PM Microsoft-Windows-Wininit 14 None Credential Guard configuration: 0x0, 0 Warning 11/13/2025 5:59:31 PM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 11/13/2025 5:59:30 PM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Warning 11/13/2025 5:59:30 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Warning 11/13/2025 5:59:30 PM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Information 11/13/2025 5:59:29 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/13/2025 5:59:29 PM NETwNe64 7036 None The \Device\NDMP3 service entered the Intel(R) Centrino(R) Wireless-N 2230 #2 state. Information 11/13/2025 5:59:28 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 3 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/13/2025 5:59:28 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 1 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/13/2025 5:59:28 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 2 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/13/2025 5:59:28 PM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 0 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/13/2025 5:59:28 PM Microsoft-Windows-Ntfs 98 None Volume \\?\Volume{df4bd8a4-f614-4d33-bbb6-6885459a0935} (\Device\HarddiskVolume1) is healthy. No action is needed. Information 11/13/2025 5:59:28 PM Microsoft-Windows-Ntfs 98 None Volume D: (\Device\HarddiskVolume5) is healthy. No action is needed. Information 11/13/2025 5:59:28 PM Microsoft-Windows-Kernel-Power 172 (203) Connectivity state in standby: Disconnected, Reason: NIC compliance Information 11/13/2025 5:59:28 PM Microsoft-Windows-FilterManager 6 None File System Filter 'npsvctrig' (10.0, ‎2025‎-‎01‎-‎05T18:41:12.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:27 PM Microsoft-Windows-FilterManager 6 None File System Filter 'UCPD' (10.0, ‎2006‎-‎08‎-‎28T03:56:22.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:27 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileCrypt' (10.0, ‎2002‎-‎03‎-‎01T03:12:42.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:27 PM Microsoft-Windows-Ntfs 98 None Volume C: (\Device\HarddiskVolume4) is healthy. No action is needed. Information 11/13/2025 5:59:27 PM Microsoft-Windows-FilterManager 6 None File System Filter 'WdFilter' (10.0, ‎1977‎-‎06‎-‎03T08:32:50.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:27 PM Microsoft-Windows-FilterManager 6 None File System Filter 'Wof' (10.0, ‎2090‎-‎03‎-‎16T10:56:17.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:27 PM Microsoft-Windows-FilterManager 6 None File System Filter 'FileInfo' (10.0, ‎2062‎-‎12‎-‎22T21:21:06.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 5:59:27 PM Microsoft-Windows-HAL 16 None The iommu fault reporting has been initialized. Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-General 20 (6) "The leap second configuration has been updated. Reason: Leap second data initialized from registry during boot Leap seconds enabled: true New leap second count: 0 Old leap second count: 0" Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-Boot 30 (21) The firmware reported boot metrics. Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-Boot 32 (58) The bootmgr spent 0 ms waiting for user input. Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-Boot 18 (57) There are 0x1 boot options on this system. Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-Boot 27 (33) The boot type was 0x0. Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-Boot 25 (32) The boot menu policy was 0x1. Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-Boot 238 (101) EFI time zone bias: 2047. Daylight flags: 0 Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-Boot 20 (31) The last shutdown's success status was true. The last boot's success status was true. Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-Boot 153 (62) Virtualization-based security (policies: 0) is disabled. Information 11/13/2025 5:59:26 PM Microsoft-Windows-Kernel-General 12 (1) The operating system started at system time ‎2025‎-‎11‎-‎14T01:59:26.500000000Z. Information 11/13/2025 5:59:17 PM Microsoft-Windows-Kernel-General 13 (2) The operating system is shutting down at system time ‎2025‎-‎11‎-‎14T01:59:17.076484700Z. Information 11/13/2025 5:59:16 PM Microsoft-Windows-Kernel-Power 109 (103) "The kernel power manager has initiated a shutdown transition. Shutdown Reason: Kernel API" Information 11/13/2025 5:59:13 PM Microsoft-Windows-WLAN-AutoConfig 4001 None "WLAN AutoConfig service has successfully stopped. " Information 11/13/2025 5:59:32 PM EventLog 6013 None The system uptime is 5 seconds. Information 11/13/2025 5:59:32 PM EventLog 6005 None The Event log service was started. Information 11/13/2025 5:59:32 PM EventLog 6009 None Microsoft (R) Windows (R) 10.00. 19045 Multiprocessor Free. Information 11/13/2025 5:59:13 PM Microsoft-Windows-Dhcp-Client 50037 Service State Event DHCPv4 client service is stopped. ShutDown Flag value is 1 Information 11/13/2025 5:59:13 PM Microsoft-Windows-Dhcp-Client 50106 Service State Event DHCPv4 is waiting on DHCPv6 service to stop Information 11/13/2025 5:59:13 PM Microsoft-Windows-DHCPv6-Client 51057 Service State Event DHCPv6 client service stop is almost done.DHCP Context Ref count is 1 Information 11/13/2025 5:59:13 PM Microsoft-Windows-DHCPv6-Client 51057 Service State Event DHCPv6 client service stop is almost done.DHCP Context Ref count is 1 Information 11/13/2025 5:59:13 PM Microsoft-Windows-DHCPv6-Client 51047 Service State Event DHCPv6 client service is stopped. ShutDown Flag value is 1 Information 11/13/2025 5:59:13 PM Microsoft-Windows-Dhcp-Client 50105 Service State Event DHCPv4 client ProcessDHCPRequestForever received TERMINATE_EVENT Information 11/13/2025 5:59:13 PM Microsoft-Windows-Dhcp-Client 50104 Service State Event DHCPv4 client received shutdown notification Information 11/13/2025 5:59:13 PM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎14T01:59:13.191126000Z from ‎2025‎-‎11‎-‎14T01:59:13.180902800Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 5484)." Information 11/13/2025 5:59:13 PM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/13/2025 5:59:13 PM EventLog 6006 None The Event log service was stopped. Information 11/13/2025 5:59:04 PM Microsoft-Windows-Winlogon 7002 (1102) User Logoff Notification for Customer Experience Improvement Program Information 11/13/2025 5:59:02 PM User32 1074 None "The process C:\WINDOWS\system32\svchost.exe (DESKTOP-JGMFQDF) has initiated the restart of computer DESKTOP-JGMFQDF on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Service pack (Planned) Reason Code: 0x80020010 Shutdown Type: restart Comment: " Information 11/13/2025 12:00:00 PM EventLog 6013 None The system uptime is 9618 seconds. Information 11/13/2025 10:30:36 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/13/2025 10:13:32 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/13/2025 9:56:28 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/13/2025 9:51:53 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/13/2025 9:51:53 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Information 11/13/2025 9:49:55 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/13/2025 9:49:37 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Information 11/13/2025 9:49:27 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/13/2025 9:49:22 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 2025-11 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5071959) Information 11/13/2025 9:49:02 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO Information 11/13/2025 9:49:00 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.ZuneVideo_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/13/2025 9:48:59 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO Information 11/13/2025 9:48:58 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRD29V9-MICROSOFT.MICROSOFTOFFICEHUB Information 11/13/2025 9:48:56 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/13/2025 9:48:51 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRD29V9-MICROSOFT.MICROSOFTOFFICEHUB Information 11/13/2025 9:48:51 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9N7V66BG7XT8-Microsoft.WindowsAppRuntime.1.7 Information 11/13/2025 9:48:47 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9NHT9RB2F4HD-Microsoft.Copilot Information 11/13/2025 9:48:40 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9NHT9RB2F4HD-Microsoft.Copilot Information 11/13/2025 9:48:40 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9N7V66BG7XT8-Microsoft.WindowsAppRuntime.1.7 Information 11/13/2025 9:48:33 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.WindowsAppRuntime.1.8_8000.675.1142.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/13/2025 9:47:10 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.WindowsAppRuntime.1.8_8000.675.1142.0_x86__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/13/2025 9:46:06 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.ZuneVideo_10.25101.10031.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/13/2025 9:45:45 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.MicrosoftOfficeHub_19.2511.41111.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/13/2025 9:45:40 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9N7V66BG7XT8-Microsoft.WindowsAppRuntime.1.7 Information 11/13/2025 9:42:52 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:42:40 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:42:40 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:42:32 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: 9WZDNCRFHWD2-Microsoft.MicrosoftSolitaireCollection Information 11/13/2025 9:42:32 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:42:32 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:42:30 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.MicrosoftSolitaireCollection_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/13/2025 9:42:29 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: 9WZDNCRFHWD2-Microsoft.MicrosoftSolitaireCollection Information 11/13/2025 9:42:18 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.MicrosoftSolitaireCollection_4.24.11040.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/13/2025 9:39:24 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/13/2025 9:38:59 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:38:59 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:38:59 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:38:34 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.WindowsAppRuntime.1.7_7000.676.1651.0_x86__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/13/2025 9:38:31 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/13/2025 9:37:11 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:37:11 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:36:35 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:36:35 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:36:35 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:36:34 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Windows\AppRepository\Packages\Microsoft.WindowsAppRuntime.1.7_7000.676.1651.0_x64__8wekyb3d8bbwe\ActivationStore.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/13/2025 9:36:27 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Information 11/13/2025 9:34:46 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:33:33 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-Provisioning-Sequence.dat was cleared updating 0 keys and creating 0 modified pages. Information 11/13/2025 9:32:46 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/13/2025 9:30:06 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.198.0) - Current Channel (Broad) Information 11/13/2025 9:29:11 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.441.198.0) - Current Channel (Broad) Information 11/13/2025 9:28:48 AM Microsoft-Windows-WindowsUpdateClient 19 Windows Update Agent Installation Successful: Windows successfully installed the following update: Windows Malicious Software Removal Tool x64 - v5.137 (KB890830) Information 11/13/2025 9:28:31 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start. Warning 11/13/2025 9:25:41 AM Microsoft-Windows-DistributedCOM 10016 None "The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97} to the user DESKTOP-JGMFQDF\User SID (S-1-5-21-586959677-3130707908-1664603102-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool." Information 11/13/2025 9:25:41 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy\Settings\settings.dat was cleared updating 2 keys and creating 1 modified pages. Information 11/13/2025 9:25:14 AM Microsoft-Windows-WindowsUpdateClient 43 Windows Update Agent Installation Started: Windows has started installing the following update: Windows Malicious Software Removal Tool x64 - v5.137 (KB890830) Error 11/13/2025 9:24:39 AM Microsoft-Windows-TPM-WMI 1801 None "Secure Boot CA/keys need to be updated. This device signature information is included here. DeviceAttributes: BaseBoardManufacturer:INTEL Corporation;FirmwareManufacturer:American Megatrends Inc.;FirmwareVersion:5.6.5;OEMModelNumber:To be filled by O.E.M.;OEMModelBaseBoard:CRESCENTBAY;OEMModelSystemFamily:To be filled by O.E.M.;OEMManufacturerName:To be filled by O.E.M.;OEMModelSKU:To be filled by O.E.M.;OSArchitecture:amd64; BucketId: 3172bfdf51002a90ec09ce6a4c3dd16df4a8a200aa84b1d0136a4916f76764e2 BucketConfidenceLevel: UpdateType: 0 HResult: The operation completed successfully." Information 11/13/2025 9:23:49 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\AD2F1837.HPPrinterControl_v10z8vjag6ke6\Settings\settings.dat was cleared updating 3 keys and creating 1 modified pages. Information 11/13/2025 9:23:46 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 2 keys and creating 1 modified pages. Information 11/13/2025 9:23:24 AM Service Control Manager 7040 None The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start. Information 11/13/2025 9:22:29 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from auto start to demand start. Information 11/13/2025 9:22:29 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\System32\SMI\Store\Machine\SCHEMA.DAT was cleared updating 15930 keys and creating 2705 modified pages. Information 11/13/2025 9:22:20 AM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎13T17:22:20.938157700Z from ‎2025‎-‎11‎-‎13T17:22:20.937166400Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 5484)." Information 11/13/2025 9:22:20 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/13/2025 9:22:20 AM Microsoft-Windows-Time-Service 35 None The time service is now synchronizing the system time with the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123) with reference id 494637363. Current local stratum number is 4. Information 11/13/2025 9:22:20 AM Microsoft-Windows-Kernel-General 1 (5) "The system time has changed to ‎2025‎-‎11‎-‎13T17:22:20.937166400Z from ‎2025‎-‎11‎-‎13T17:22:07.476485800Z. Change Reason: An application or system component changed the time. Process: '\Device\HarddiskVolume4\Windows\System32\svchost.exe' (PID 5484)." Information 11/13/2025 9:22:20 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/13/2025 9:22:05 AM Service Control Manager 7040 None The start type of the Windows Modules Installer service was changed from demand start to auto start. Information 11/13/2025 9:21:53 AM Microsoft-Windows-Time-Service 37 None The time provider NtpClient is currently receiving valid time data from time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->51.145.123.29:123). Warning 11/13/2025 9:21:51 AM 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." Warning 11/13/2025 9:21:51 AM 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.WscBrokerManager 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." Warning 11/13/2025 9:21:51 AM 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.SecurityAppBroker 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." Information 11/13/2025 9:21:51 AM Microsoft-Windows-Time-Service 158 None The time provider 'VMICTimeProvider' has indicated that the current hardware and operating environment is not supported and has stopped. This behavior is expected for VMICTimeProvider on non-HyperV-guest environments. This may be the expected behavior for the current provider in the current operating environment as well. Information 11/13/2025 9:21:37 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:21:22 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:21:17 AM Microsoft-Windows-WindowsUpdateClient 44 Windows Update Agent Windows Update started downloading an update. Information 11/13/2025 9:21:14 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization\State\dosvcState.dat was cleared updating 4 keys and creating 2 modified pages. Information 11/13/2025 9:20:51 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.YourPhone_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\1de7d01bf2e5d781_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/13/2025 9:20:49 AM Microsoft-Windows-WER-SystemErrorReporting 1018 None The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space. Warning 11/13/2025 9:20:42 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/13/2025 9:20:42 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/13/2025 9:20:42 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Warning 11/13/2025 9:20:42 AM Microsoft-Windows-Kernel-Processor-Power 37 (7) The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report. Information 11/13/2025 9:20:35 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\ProgramData\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\S-1-5-21-586959677-3130707908-1664603102-1001\SystemAppData\Helium\Cache\c75fb7e1f4b8ebe1_COM15.dat was cleared updating 1 keys and creating 1 modified pages. Information 11/13/2025 9:20:35 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 5 keys and creating 1 modified pages. Information 11/13/2025 9:20:34 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\Settings\settings.dat was cleared updating 13 keys and creating 3 modified pages. Error 11/13/2025 9:20:26 AM Microsoft-Windows-WER-SystemErrorReporting 1001 None The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x000000000000003f, 0x00000000000d692b, 0x00000000affa3091, 0x00000000f09faa97). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e072616f-c72c-403b-9ff7-269d50fd8452. Information 11/13/2025 9:20:19 AM Microsoft-Windows-Kernel-General 15 (10) Hive \??\C:\WINDOWS\System32\config\COMPONENTS was reorganized with a starting size of 51458048 bytes and an ending size of 46718976 bytes. Information 11/13/2025 9:20:18 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\Settings\settings.dat was cleared updating 2 keys and creating 1 modified pages. Error 11/13/2025 9:20:14 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/13/2025 9:20:14 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/13/2025 9:20:14 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/13/2025 9:20:14 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/13/2025 9:20:14 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/13/2025 9:20:14 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/13/2025 9:20:14 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Error 11/13/2025 9:20:14 AM NetBT 4319 None A duplicate name has been detected on the TCP network. The IP address of the computer that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state. Information 11/13/2025 9:20:08 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\Settings\settings.dat was cleared updating 3 keys and creating 1 modified pages. Warning 11/13/2025 9:20:03 AM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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 11/13/2025 9:20:03 AM Microsoft-Windows-DistributedCOM 10016 None "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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." Information 11/13/2025 9:19:50 AM Service Control Manager 7026 None "The following boot-start or system-start driver(s) did not load: dam" Information 11/13/2025 9:19:45 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\AppData\Local\Microsoft\Windows\UsrClass.dat was cleared updating 4640 keys and creating 578 modified pages. Information 11/13/2025 9:19:45 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\Users\User\ntuser.dat was cleared updating 1768 keys and creating 178 modified pages. Information 11/13/2025 9:19:45 AM Microsoft-Windows-Winlogon 7001 (1101) User Logon Notification for Customer Experience Improvement Program Error 11/13/2025 9:19:44 AM Service Control Manager 7034 None The MediaMTX service terminated unexpectedly. It has done this 1 time(s). Error 11/13/2025 9:19:44 AM Service Control Manager 7024 None "The MediaMTX service terminated with the following service-specific error: The system cannot find the path specified." Information 11/13/2025 9:19:41 AM Microsoft-Windows-WLAN-AutoConfig 4000 None "WLAN AutoConfig service has successfully started. " Information 11/13/2025 9:19:39 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\bbimigrate\BBI was cleared updating 1 keys and creating 1 modified pages. Information 11/13/2025 9:19:38 AM Microsoft-Windows-DHCPv6-Client 51046 Service State Event DHCPv6 client service is started Information 11/13/2025 9:19:38 AM Microsoft-Windows-Dhcp-Client 50103 Service State Event DHCPv4 client registered for shutdown notification Information 11/13/2025 9:19:38 AM Microsoft-Windows-Dhcp-Client 50036 Service State Event DHCPv4 client service is started Information 11/13/2025 9:19:38 AM Microsoft-Windows-FilterManager 6 None File System Filter 'bindflt' (10.0, ‎2091‎-‎04‎-‎15T15:55:03.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 9:19:38 AM Microsoft-Windows-FilterManager 6 None File System Filter 'storqosflt' (10.0, ‎2038‎-‎12‎-‎03T01:18:20.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 9:19:37 AM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 9:19:37 AM Microsoft-Windows-FilterManager 1 None File System Filter 'CldFlt' (Version 10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) unloaded successfully. Information 11/13/2025 9:19:37 AM Microsoft-Windows-FilterManager 6 None File System Filter 'CldFlt' (10.0, ‎2032‎-‎05‎-‎25T00:06:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 9:19:37 AM Microsoft-Windows-FilterManager 6 None File System Filter 'luafv' (10.0, ‎1996‎-‎01‎-‎27T04:16:28.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 9:19:37 AM Microsoft-Windows-FilterManager 6 None File System Filter 'wcifs' (10.0, ‎2043‎-‎11‎-‎04T03:04:53.000000000Z) has successfully loaded and registered with Filter Manager. Information 11/13/2025 9:19:37 AM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection #2 Network link has been established at 1Gbps full duplex. " Information 11/13/2025 9:19:37 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\BBI was cleared updating 418 keys and creating 88 modified pages. Information 11/13/2025 9:19:37 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\ServiceProfiles\LocalService\NTUSER.DAT was cleared updating 74 keys and creating 16 modified pages. Information 11/13/2025 9:19:37 AM e1rexpress 32 None "Intel(R) I211 Gigabit Network Connection Network link has been established at 1Gbps full duplex. " Information 11/13/2025 9:19:37 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \??\C:\WINDOWS\ServiceProfiles\NetworkService\NTUSER.DAT was cleared updating 93 keys and creating 12 modified pages. Information 11/13/2025 9:19:36 AM Microsoft-Windows-Directory-Services-SAM 16983 None "The security account manager is now logging periodic summary events for remote clients that call legacy password change or set RPC methods. For more information please see https://go.microsoft.com/fwlink/?linkid=2150956. " Information 11/13/2025 9:19:36 AM Microsoft-Windows-Directory-Services-SAM 16977 None "The domain is configured with the following minimum password length-related settings. MinimumPasswordLength: 0 RelaxMinimumPasswordLengthLimits: 0 MinimumPasswordLengthAudit: -1 For more information see https://go.microsoft.com/fwlink/?LinkId=2097191. " Information 11/13/2025 9:19:36 AM Microsoft-Windows-Directory-Services-SAM 16962 None "Remote calls to the SAM database are being restricted using the default security descriptor: O:SYG:SYD:(A;;RC;;;BA). For more information please see http://go.microsoft.com/fwlink/?LinkId=787651." Information 11/13/2025 9:19:36 AM Microsoft-Windows-Wininit 14 None Credential Guard configuration: 0x0, 0 Warning 11/13/2025 9:19:36 AM BTHUSB 34 None The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x2491f7fffff, got 0x1f7fffff. Low Energy peripheral role functionality will not be available. Information 11/13/2025 9:19:36 AM BTHUSB 18 None Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Information 11/13/2025 9:19:34 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \Device\HarddiskVolume2\EFI\Microsoft\Boot\BCD was cleared updating 61 keys and creating 8 modified pages. Information 11/13/2025 9:19:34 AM Microsoft-Windows-Kernel-General 24 (11) The time zone information was refreshed with exit reason 0. Current time zone bias is 480. Information 11/13/2025 9:19:34 AM Microsoft-Windows-Kernel-General 15 (10) Hive \SystemRoot\System32\Config\SOFTWARE was reorganized with a starting size of 82391040 bytes and an ending size of 81715200 bytes. Warning 11/13/2025 9:19:33 AM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection #2 Network link is disconnected. " Warning 11/13/2025 9:19:33 AM e1rexpress 27 None "Intel(R) I211 Gigabit Network Connection Network link is disconnected. " Information 11/13/2025 9:19:31 AM NETwNe64 7036 None The \Device\NDMP4 service entered the Intel(R) Centrino(R) Wireless-N 2230 #2 state. Information 11/13/2025 9:19:31 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 3 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/13/2025 9:19:31 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 1 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/13/2025 9:19:31 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 2 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/13/2025 9:19:31 AM Microsoft-Windows-Kernel-Processor-Power 55 (47) "Processor 0 in group 0 exposes the following power management capabilities: Idle state type: ACPI Idle (C) States (3 state(s)) Performance state type: ACPI Performance (P) / Throttle (T) States Nominal Frequency (MHz): 2301 Maximum performance percentage: 100 Minimum performance percentage: 32 Minimum throttle percentage: 32" Information 11/13/2025 9:19:31 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\DEFAULT was cleared updating 266 keys and creating 47 modified pages. Information 11/13/2025 9:19:31 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\SECURITY was cleared updating 75 keys and creating 4 modified pages. Information 11/13/2025 9:19:31 AM Microsoft-Windows-Kernel-General 16 None The access history in hive \SystemRoot\System32\Config\SAM was cleared updating 69 keys and creating 8 modified pages. Information 11/13/2025 9:19:31 AM Microsoft-Windows-Ntfs 98 None Volume \\?\Volume{df4bd8a4-f614-4d33-bbb6-6885459a0935} (\Device\HarddiskVolume1) is healthy. No action is needed.