# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"02/13/2022" Time:"00:00:35.6034117" # Scanned Hardware Computer: BaseBoard Manufacturer:"ASRock" BIOS Mode:"UEFI" BIOS Version/Date:"American Megatrends Inc. P1.30 , 06/05/2020 12:00 AM" CD or DVD:"Not Available" Embedded Controller Version:"255.255" Platform Role:"Desktop" Processor:"Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz , GenuineIntel" Secure Boot State:"Off" SMBIOS Version:"3.2" Sound Card:"NVIDIA Virtual Audio Device (Wave Extensible) (WDM)" Sound Card:"Realtek High Definition Audio" Sound Card:"USB Audio Device" Sound Card:"USB Audio Device" Sound Card:"NVIDIA High Definition Audio" System Manufacturer:"To Be Filled By O.E.M." System Model:"To Be Filled By O.E.M." System SKU:"To Be Filled By O.E.M." System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"Not Available" - "NVIDIA GeForce GTX 1060 3GB" Adapter Compatibility:"NVIDIA" Adapter DAC Type:"Integrated RAMDAC" Adapter RAM:"3.00 GB" Availability:"Running or Full Power" Bits Per Pixel:"32" Caption:"NVIDIA GeForce GTX 1060 3GB" CoInstallers:"oem26.inf,Section025,Integrated RAMDAC,NVIDIA GeForce GTX 1060 3GB" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"nvlddmkm.sys" Driver Date:"01/28/2022 02:00 AM" Driver Path:"C:\Windows\system32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvlddmkm.sys" Driver Provider:"NVIDIA" Driver Version:"30.0.15.1165" INF:"oem26.inf" INF Section:"Section025" Install Date:"Not Available" Installed Drivers:"C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumdx.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 1, device 0, function 0" Manufacturer:"NVIDIA" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_10DE&DEV_1C02&SUBSYS_85B11043&REV_A1\4&30760922&0&0008" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"144 Hz" Refresh Rate - Maximum:"144 Hz" Refresh Rate - Minimum:"50 Hz" Resolution:"1920 X 1080" Scan Mode:"Noninterlaced" Service Name:"nvlddmkm" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"NVIDIA GeForce GTX 1060 3GB" - "Memory" Physical Memory (Available):"10.53 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.91 GB" - "BANK 2" Capacity:"16 GB" Channel:"ChannelB-DIMM0" Configured Clock Speed:"3200 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"DIMM" Interleave Position:"Noninterleaved" Manufacturer:"04CD" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"F4-3200C16-16GTZN" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"P1.30, ALASKA - 1072009" Caption:"Motherboard" Chipset:"Not Available" Date:"06/05/2020 03:00 AM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"ASRock" Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"Z490M-ITX/ac" Serial Number:"M80-D5011900631" Status:"OK" Version:"Not Available" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Intel(R) Dual Band Wireless-AC 3168" Access Point: Authentication: Availability:"Running or Full Power" - "Caption":"Intel(R) Dual Band Wireless-AC 3168" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Dual+Band+Wireless+AC+3168" Channel: Cipher: CoInstallers:"Not Available" Connection Mode: Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"Netwtw04.sys" Driver Date:"01/19/2020 12:00 AM" Driver Path:"C:\Windows\system32\drivers\Netwtw04.sys" Driver Provider:"Intel" Driver Version:"19.51.28.1" Index:"0001" INF:"oem64.inf" INF Section:"Install_MPCIEX_GENM2_3168_AC_HMC_WINT_64_AC" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02/13/2022 01:53 PM" Location:"PCI bus 3, device 0, function 0" MAC Address:"D8:3B:BF:FB:A8:1A" Manufacturer:"Intel Corporation" Media Type: Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{DB5EA634-A905-4EE9-9D70-DDF65E94FBAB}" Network Name:"Wi-Fi" Network Type: Number of VLANs:"0" PNP Device ID:"PCI\VEN_8086&DEV_24FB&SUBSYS_21108086&REV_10\4&3B5BA214&0&00E0" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Dual Band Wireless-AC 3168" Profile: Radio Type: Receive Rate: Service Name:"Netwtw04" Signal Strength: State:"disconnected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)" *PacketCoalescing:Packet Coalescing:"Enabled (1)" *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)" *PMNSOffload:NS offload for WoWLAN:"Enabled (1)" *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"Auto (1)" CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)" FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)" IbssTxPower:Transmit Power:"5. Highest (100)" IEEE11nMode:802.11n/ac Wireless Mode:"802.11ac (2)" MIMOPowerSaveMode:MIMO Power Save Mode:"Auto SMPS (0)" RoamAggressiveness:Roaming Aggressiveness:"3. Medium (2)" RoamingPreferredBandType:Preferred Band:"1. No Preference (0)" ThroughputBoosterEnabled:Throughput Booster:"Disabled (0)" uAPSDSupport:U-APSD support:"Disabled (0)" WirelessMode:802.11a/b/g Wireless Mode:"6. Dual Band 802.11a/b/g (34)" - "Intel(R) Ethernet Connection (11) I219-V" Availability:"Running or Full Power" - "Caption":"Intel(R) Ethernet Connection (11) I219-V" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Ethernet+Connection+(11)+I219+V" CoInstallers:"Not Available" Default IP Gateway:"192.168.8.1" DHCP Enabled:"Yes" DHCP Lease Expires:"02/14/2022 01:54 PM" DHCP Lease Obtained:"02/13/2022 01:54 PM" DHCP Server:"192.168.8.1" Driver:"e1d68x64.sys" Driver Date:"01/05/2021 12:00 AM" Driver Path:"C:\Windows\system32\DriverStore\FileRepository\e1d68x64.inf_amd64_d31d833ebd189f40\e1d68x64.sys" Driver Provider:"Intel" Driver Version:"12.19.1.35" ETrackID:"Not Available" Index:"0014" INF:"oem66.inf" INF Section:"E0D4D.10.0.1.19H1" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.8.107;fe80::3116:db1:c53f:998b" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02/13/2022 01:53 PM" Location:"PCI bus 0, device 31, function 6" MAC Address:"A8:A1:59:2E:31:00" Manufacturer:"Intel" Media Type: Net Connection ID:"Ethernet 2" NetCfgInstanceId:"{5E7E512A-C50C-4C60-B351-E81FFCFC5F31}" Number of VLANs:"0" NVM Version:"Not Available" Part Number:"FFFFFF-0FF" PNP Device ID:"PCI\VEN_8086&DEV_0D4D&SUBSYS_0D4D1849&REV_00\3&11583659&0&FE" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: Yes" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Ethernet Connection (11) I219-V" Service Name:"e1dexpress" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Packet:"Disabled (1514)" *LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)" *ModernStandbyWoLMagicPacket:Wake from S0ix on Magic Packet:"Enabled (1)" *NumRssQueues:Maximum Number of RSS Queues:"2 Queues (2)" *PMARPOffload:Protocol ARP Offload:"Enabled (1)" *PMNSOffload:Protocol NS Offload:"Enabled (1)" *PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enabled (3)" *PtpHardwareTimestamp:PTP Hardware Timestamp:"Disabled (0)" *ReceiveBuffers:Receive Buffers:"256 (256)" *RSS:Receive Side Scaling:"Enabled (1)" *RSSProfile:RSS load balancing profile:"ClosestProcessor (1)" *SoftwareTimestamp:Software Timestamp:"Disabled (0)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *TransmitBuffers:Transmit Buffers:"512 (512)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" AdaptiveIFS:Adaptive Inter-Frame Spacing:"Disabled (0)" AutoPowerSaveModeEnabled:Link Speed Battery Saver:"Disabled (0)" EEELinkAdvertisement:Energy Efficient Ethernet:"On (1)" EnablePME:Enable PME:"Enabled (1)" ITR:Interrupt Moderation Rate:"Adaptive (65535)" LinkNegotiationProcess:Legacy Switch Compatibility Mode:"Disabled (1)" LogLinkStateEvent:Log Link State Event:"Enabled (51)" MasterSlave:Gigabit Master Slave Mode:"Auto Detect (0)" ReduceSpeedOnPowerDown:Reduce Speed On Power Down:"Enabled (1)" SipsEnabled:System Idle Power Saver:"Disabled (0)" ULPMode:Ultra Low Power Mode:"Enabled (1)" WaitAutoNegComplete:Wait for Link:"Auto Detect (2)" WakeOnLink:Wake on Link Settings:"Disabled (0)" - "Realtek Gaming 2.5GbE Family Controller" Availability:"Running or Full Power" Caption:"Realtek Gaming 2.5GbE Family Controller" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"rt640x64.sys" Driver Date:"12/31/2020 12:00 AM" Driver Path:"C:\Windows\system32\drivers\rt640x64.sys" Driver Provider:"Realtek" Driver Version:"10.46.1231.2020" Index:"0003" INF:"oem12.inf" INF Section:"RTL8125BG.ndi.NT" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02/13/2022 01:53 PM" Location:"PCI bus 4, device 0, function 0" MAC Address:"A8:A1:59:2E:31:02" Manufacturer:"Realtek" Media Type: Net Connection ID:"Ethernet" NetCfgInstanceId:"{AB852FF2-B2E0-4CCA-ACDF-A14B85F7A514}" Number of VLANs:"0" PNP Device ID:"PCI\VEN_10EC&DEV_8125&SUBSYS_81681849&REV_05\4&32AC88EE&0&00E3" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Realtek Gaming 2.5GbE Family Controller" Service Name:"rt640x64" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" *EEE:Energy-Efficient Ethernet:"Disabled (0)" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Frame:"Disabled (1514)" *LsoV2IPv4:Large Send Offload v2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload v2 (IPv6):"Enabled (1)" *ModernStandbyWoLMagicPacket:Wake on magic packet when system is in the S0ix power state:"Disabled (0)" *NumRssQueues:Maximum Number of RSS Queues:"2 Queues (2)" *PMARPOffload:ARP Offload:"Enabled (1)" *PMNSOffload:NS Offload:"Enabled (1)" *PriorityVLANTag:Priority & VLAN:"Priority & VLAN Enabled (3)" *ReceiveBuffers:Receive Buffers:"512 (512)" *RSS:Receive Side Scaling:"Enabled (1)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *TransmitBuffers:Transmit Buffers:"128 (128)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on pattern match:"Enabled (1)" AdvancedEEE:Advanced EEE:"Disabled (0)" EEEMaxSupportSpeed:EEE Max Support Speed:"1.0 Gbps Full Duplex (1000)" EnableGreenEthernet:Green Ethernet:"Enabled (1)" GigaLite:Gigabit Lite:"Enabled (1)" PowerSavingMode:Power Saving Mode:"Enabled (1)" RegVlanid:VLAN ID:"0 (0)" S5WakeOnLan:Shutdown Wake-On-Lan:"Enabled (1)" WolShutdownLinkSpeed:WOL & Shutdown Link Speed:"10 Mbps First (0)" - "Surfshark Tunnel" Availability:"Running or Full Power" Caption:"Surfshark Tunnel" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"No" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"wintunshark.sys" Driver Date:"08/10/2020 12:00 AM" Driver Path:"C:\Windows\system32\DRIVERS\wintunshark.sys" Driver Provider:"Surfshark Ltd" Driver Version:"0.8.0.0" Index:"0018" INF:"oem15.inf" INF Section:"Wintunshark.Install" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02/13/2022 01:53 PM" Location:"Not Available" MAC Address:"Not Available" Manufacturer:"Surfshark Ltd" Media Type: Net Connection ID:"wintunshark0" NetCfgInstanceId:"{A4AE44AD-BF67-BD5C-0B51-3541B8B2420B}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0000" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Wintunshark Userspace Tunnel" Service Name:"wintunshark" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Not Available" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: - "TAP-Surfshark Windows Adapter V9" Availability:"Running or Full Power" Caption:"TAP-Surfshark Windows Adapter V9" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"tapsurfshark.sys" Driver Date:"08/01/2018 12:00 AM" Driver Path:"C:\Windows\system32\drivers\tapsurfshark.sys" Driver Provider:"TAP-Surfshark Windows Provider V9" Driver Version:"11.57.35.775" Index:"0016" INF:"oem16.inf" INF Section:"tapsurfshark.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02/13/2022 01:53 PM" Location:"Not Available" MAC Address:"00:FF:6E:73:38:54" Manufacturer:"TAP-Surfshark Windows Provider V9" Media Type: Net Connection ID:"Ethernet 3" NetCfgInstanceId:"{6E733854-EFE1-4E04-9E6D-B8023DD4B08A}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0001" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"TAP-Surfshark Windows Adapter V9" Service Name:"tapsurfshark" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" AllowNonAdmin:Non-Admin Access:"Allowed (1)" MediaStatus:Media Status:"Application Controlled (0)" MTU:MTU:"1500 (1500)" - "Operating System" .Net Framework Version:"2.0,3.0,3.5,4.0,4.8" Boot Device:"\Device\HarddiskVolume1" Locale:"United States" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Pro" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"2.38 GB" Physical Memory (Available):"10.54 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.91 GB" System Directory:"C:\Windows\system32" Version:"10.0.19043 Build 19043" Virtual Memory (Available):"10.20 GB" Virtual Memory (Total):"18.29 GB" Windows Directory:"C:\Windows" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [17/08/2021]" KB2151757:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [17/08/2021]" KB2467173:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [17/08/2021]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [17/08/2021]" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB5000736:"Update [4/9/2021]" KB5005699:"Security Update [9/25/2021]" KB5006753:"Update [11/10/2021]" KB5007273:"Update [12/17/2021]" KB5009467:"Update [2/9/2022]" KB5010342:"Security Update [2/9/2022]" KB5011352:"Security Update [2/9/2022]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [17/08/2021]" KB982573:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [17/08/2021]" SP1:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [Not Available]" SP1:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [Not Available]" - "Processor" - "Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 165 Stepping 5" - "Chipset Name":"Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i9+10900K+CPU+" CPU Speed:"3.70 GHz" Current Voltage:"1.6 volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00 AM" Driver Path:"C:\Windows\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.19041.546" Ext. Family:"Not Available" Family:"Not Available" FPO:"Not Available" INF:"cpu.inf" INF Section:"IntelPPM_Inst.NT" Install Date:"Not Available" Last Error Code:"Not Available" Level 1 Cache:"10 x 640 KB" Level 2 Cache:"10 x 2560 KB" Level 3 Cache:"20 MB" Load:"0%" Manufacturer:"GenuineIntel" Model:"165" Name:"Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz" Number of Cores:"10" Number of Cores Enabled:"10" Number of Logical Processors:"20" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000A0655" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"5" Version:"Not Available" - "Storage" - "Sabrent Rocket Q" Capablities:"Random Access, Supports Writing" Caption:"Sabrent Rocket Q" Cylinder - Total:"243201" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.19041.789" Error Code:"Device is working properly" Firmware Revision:"RKT30Q.1" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"Sabrent Rocket Q" Name:"\\.\PHYSICALDRIVE0" Partitions:"3" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_SABRENT_ROCKET_Q\5&289AABF6&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"1" Sectors - Per Track:"63" Sectors - Total:"3907024065" Serial Number:"6479_A737_5004_18AA." Size:"1.82 TB" Size – Available:"285.37 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"62016255" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Not Available" Serial Number:"72F4A68C" Size:"1862.40 GB" Size – Available:"285.38 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 1:35:57 PM on ‎2/‎13/‎2022 was unexpected. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 23 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{AB852FF2-B2E0-4CCA-ACDF-A14B85F7A514} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{AB852FF2-B2E0-4CCA-ACDF-A14B85F7A514} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{D6A57CBB-86A1-4ABA-8555-9797D272C35A} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 5:18:23 PM on ‎2/‎11/‎2022 was unexpected. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B68-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_bb110 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The RasMan service depends on the Dnscache service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The IKEEXT service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Wcmsvc service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Dnscache service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1068" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- The netprofm service depends on the NlaSvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The NlaSvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The nsi service depends on the nsiproxy service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The Dhcp service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 2:47:41 PM on ‎2/‎10/‎2022 was unexpected. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B68-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_b7ee8 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The RasMan service depends on the Dnscache service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The IKEEXT service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Wcmsvc service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Dnscache service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1068" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- The netprofm service depends on the NlaSvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The NlaSvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The nsi service depends on the nsiproxy service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The Dhcp service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The AsusUpdateCheck service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The XTU3SERVICE service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the XTU3SERVICE service to connect. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Intel(R) TPM Provisioning Service service to connect. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 22 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{46C241A3-CBC1-4297-903C-CD30D7C32C7A} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 22 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{1E98FED9-0018-45F3-8871-00DDAA27C5CC} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 22 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{CEBE0209-CDE9-4A53-95B1-E9435FCCB370} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 22 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{DA0B5549-367A-46D4-B951-DD2D52654F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 22 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ACC18E7A-7A16-4254-96FC-99D00BD97372} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 22 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{A7005F03-D01C-4664-8515-DD0A38D715B3} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The AMD User Experience Program Launcher service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The BITS service failed to start. Error 0x80004015. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B68-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_74603 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_837ec with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The NlaSvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The RasMan service depends on the Dnscache service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The IKEEXT service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Wcmsvc service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Dnscache service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The nsi service depends on the nsiproxy service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The Dhcp service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- DCOM got error "1069" attempting to start the service cdpsvc with arguments "Unavailable" in order to run the server: {284CACFE-B6F2-461A-90C3-A7ACC8353816} ------------------------------------------------------------------- The Connected Devices Platform Service service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The CDPSvc service was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The WerSvc service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The WerSvc service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The ClickToRunSvc service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The XTU3SERVICE service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The igccservice service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The Apple Mobile Device 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. ------------------------------------------------------------------- The Surfshark Shadowsocks 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. ------------------------------------------------------------------- The Surfshark Antivirus service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The Surfshark 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. ------------------------------------------------------------------- The Bonjour 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. ------------------------------------------------------------------- The PnkBstrA service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The TrkWks service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The stisvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WpnService service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The TrkWks service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The stisvc service was unable to log on as NT Authority\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The SstpSvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WinDefend service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The iphlpsvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Origin Web Helper Service service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WpnService service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The SstpSvc service was unable to log on as NT Authority\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The WinDefend service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The iphlpsvc service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The Origin Web Helper Service service was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The DPS service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The IKEEXT service depends on the BFE service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The BFE service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The BFE service was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The DPS service was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The DiagTrack service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The DiagTrack service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The LanmanWorkstation service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The LanmanWorkstation service was unable to log on as NT AUTHORITY\NetworkService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The mpssvc service depends on the BFE service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The BFE service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The BFE service was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The Spooler service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Spooler service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Wcmsvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Wcmsvc service was unable to log on as NT Authority\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The DusmSvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The DusmSvc service was unable to log on as NT Authority\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The Audiosrv service depends on the AudioEndpointBuilder service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The AudioEndpointBuilder service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The AudioEndpointBuilder service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The Themes service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The AMD External Events Utility service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 3:09:37 PM on ‎2/‎2/‎2022 was unexpected. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The AMD User Experience Program Launcher service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The AMD External Events Utility service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the AMD External Events Utility service to connect. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Crash dump initialization failed! ------------------------------------------------------------------- The previous system shutdown at 12:03:35 AM on ‎2/‎2/‎2022 was unexpected. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The AMD External Events Utility service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the AMD External Events Utility service to connect. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 11:59:56 PM on ‎2/‎1/‎2022 was unexpected. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 22 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{AB852FF2-B2E0-4CCA-ACDF-A14B85F7A514} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{19900D9B-0010-4817-94FC-3F0C576CC04E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{AB852FF2-B2E0-4CCA-ACDF-A14B85F7A514} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Device Install Service service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B68-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6d6ed with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The NlaSvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The RasMan service depends on the Dnscache service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The IKEEXT service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Wcmsvc service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Dnscache service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The nsi service depends on the nsiproxy service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The Dhcp service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The Remote Access Connection Manager service terminated with the following service-specific error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The AMD External Events Utility service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the AMD External Events Utility service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 4:44:10 PM on ‎2/‎1/‎2022 was unexpected. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {4AA0A5C4-1B9B-4F2E-99D7-99C6AEC83474} did not register with DCOM within the required timeout. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B68-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_76e6e with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The RasMan service depends on the Dnscache service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The NlaSvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The IKEEXT service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Wcmsvc service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Dnscache service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The nsi service depends on the nsiproxy service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The Dhcp service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The iPod Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Surfshark Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The Intel(R) Graphics Command Center Service service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The Intel(R) Graphics Command Center Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server Microsoft.LockApp_10.0.19041.1023_neutral__cw5n1h2txyewy!WindowsDefaultLockScreen did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 3:38:16 AM on ‎1/‎30/‎2022 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 3:11:05 AM on ‎1/‎30/‎2022 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 3:04:54 AM on ‎1/‎30/‎2022 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 2:43:04 AM on ‎1/‎30/‎2022 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 7:11:52 PM on ‎1/‎29/‎2022 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 2:34:07 PM on ‎1/‎28/‎2022 was unexpected. ------------------------------------------------------------------- The server windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.Search_1.14.2.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB93B6F1-BE76-4185-A488-A9001B105B94} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 22 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{FDB5DAF9-932E-4288-AF2A-AAEFFF527C0C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: NVIDIA - Display - 27.21.14.5671. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_64529 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The RasMan service depends on the Dnscache service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The NlaSvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The IKEEXT service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Wcmsvc service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Dnscache service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The nsi service depends on the nsiproxy service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The Dhcp service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {1A1F4206-0688-4E7F-BE03-D82EC69DF9A5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {1A1F4206-0688-4E7F-BE03-D82EC69DF9A5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Steam Client 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. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {1A1F4206-0688-4E7F-BE03-D82EC69DF9A5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The time service has detected that the system time needs to be changed by 259925 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->40.119.148.38:123) is working properly. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The time service has detected that the system time needs to be changed by 259921 seconds. The time service will not change the system time by more than 54000 seconds. Verify that your time and time zone are correct, and that the time source time.windows.com,0x9 (ntp.m|0x9|0.0.0.0:123->40.119.148.38:123) is working properly. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 5:02:31 PM on ‎1/‎21/‎2022 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 7:16:29 PM on ‎1/‎13/‎2022 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppX447jn8wbjb1qsw3jxkndb19cwgsrtrkk.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server Microsoft.Windows.Search_1.14.2.19041_neutral_neutral_cw5n1h2txyewy!ShellFeedsUI.AppXfbff151h5bmghg166fvn34ccayg70vts.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 6:09:07 PM on ‎1/‎8/‎2022 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{98FFFEAF-7A26-4976-870D-08BBB1B93085} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{4C808DAC-4688-4375-8B6E-EADFDDE782CC} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {1A1F4206-0688-4E7F-BE03-D82EC69DF9A5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 7:49:37 PM on ‎1/‎5/‎2022 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{D87AC146-4B31-4927-9588-F832D4822666} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{C1AD25ED-3CA8-4847-9723-66BEA156004A} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8BF82B85-3E26-4461-9443-D84FC084A159} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{36BB4CFC-6278-4849-83BE-3D8FE5CAAFED} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityConsentManager ------------------------------------------------------------------- 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. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXryc2qd338f5728r9gzzazav8206ba77s.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppX447jn8wbjb1qsw3jxkndb19cwgsrtrkk.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 7:16:18 PM on ‎12/‎25/‎2021 was unexpected. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: NVIDIA - Display - 27.21.14.5751. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 9:40:50 PM on ‎12/‎23/‎2021 was unexpected. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service dps with arguments "Unavailable" in order to run the server: {DDCFD26B-FEED-44CD-B71D-79487D2E5E5A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_6b178 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F87B28F1-DA9A-4F35-8EC0-800EFCF26B83} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Crash dump initialization failed! ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 8:28:57 PM on ‎12/‎23/‎2021 was unexpected. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 7:49:49 PM on ‎12/‎23/‎2021 was unexpected. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 7:23:45 PM on ‎12/‎23/‎2021 was unexpected. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 6:16:46 PM on ‎12/‎23/‎2021 was unexpected. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 6:07:31 PM on ‎12/‎23/‎2021 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Steam Client 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. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 1:21:39 PM on ‎12/‎19/‎2021 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{7F92A1A8-AEDC-4AF9-AEF0-180FC38BC6F7} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 3168 : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.1023.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9ABB8397-60BE-4664-8067-F5C03ADEC6FA} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{29A8C888-24CD-4BD7-8C4D-DF7ADE036483} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The PnkBstrA service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Surfshark Antivirus service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{91A29CF7-B85D-4B98-B2B4-5733B1B152B8} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 12:09:02 PM on ‎12/‎8/‎2021 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{1480466C-5C75-4CE9-A634-DAB94EDB4E26} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 11:58:00 AM on ‎12/‎4/‎2021 was unexpected. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 3168 : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B68-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityProvisioning ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityProvisioning ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_54085 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240009: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.353.1967.0). ------------------------------------------------------------------- The Razer Synapse Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Run the configured recovery program. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{78054736-D73E-4B2A-A1B8-6E7E346619B9} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{7042EF31-F655-4C9A-A8BE-1A8286F5035C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{4B195A45-B2DE-46B8-9282-3402EACB5030} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{EBF56F13-022D-49FD-A59F-8FBB50962B2E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{DB5EA634-A905-4EE9-9D70-DDF65E94FBAB} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{DB5EA634-A905-4EE9-9D70-DDF65E94FBAB} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{844E19BC-5368-4736-B25E-114959471734} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{DB5EA634-A905-4EE9-9D70-DDF65E94FBAB} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9C8309BE-26E3-42D6-99B8-ECBCC37EC0B9} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{1C1F74B8-0171-48B5-901D-AA6F92EAA8E8} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{DB5EA634-A905-4EE9-9D70-DDF65E94FBAB} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{1F2E67BC-69E8-494A-BC7E-3E64DA9E5515} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- 5007 - TX/CMD timeout (TfdQueue hanged) ------------------------------------------------------------------- 5007 - TX/CMD timeout (TfdQueue hanged) ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{DB5EA634-A905-4EE9-9D70-DDF65E94FBAB} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{DB5EA634-A905-4EE9-9D70-DDF65E94FBAB} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{CF41904E-69AA-476A-8D89-F477FD1213A6} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{AB852FF2-B2E0-4CCA-ACDF-A14B85F7A514} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{1D1B0BB9-42C5-4524-AABC-F0D350AEFB43} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The Steam Client 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. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{148FAC91-D001-4E9A-80C1-D06E7B7C1673} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Steam Client 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. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: NVIDIA - Display - 27.21.14.5751. ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_501da with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server: {08D9DFDF-C6F7-404A-A20F-66EEC0A609CD} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The RasMan service depends on the Dnscache service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The NlaSvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The IKEEXT service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Wcmsvc service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Dnscache service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The nsi service depends on the nsiproxy service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The Dhcp service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- The Intel(R) Content Protection HDCP Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 12:51:11 PM on ‎11/‎18/‎2021 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{12D2DE4B-D394-4476-9BC7-1003FC14BA73} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 21 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{A6AE0350-30B0-456F-AE08-FE4975BAC434} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5E7E512A-C50C-4C60-B351-E81FFCFC5F31} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{147B399B-F991-4F79-A7B2-116EA028B69E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The EQU8_39 service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- 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. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 2/13/2022, 13:58:38 Machine name: DESKTOP-MLHI9GF Machine Id: {50B5A158-1C93-47CE-9ADF-A1D18831FD39} Operating System: Windows 10 Pro 64-bit (10.0, Build 19043) (19041.vb_release.191206-1406) Language: English (Regional Setting: English) System Manufacturer: To Be Filled By O.E.M. System Model: To Be Filled By O.E.M. BIOS: P1.30 (type: UEFI) Processor: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz (20 CPUs), ~3.7GHz Memory: 16384MB RAM Available OS Memory: 16294MB RAM Page File: 8344MB used, 10381MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, no HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.0.8 DxDiag Version: 10.00.19041.0928 64bit Unicode DxDiag Previously: Crashed in system information (stage 4). Re-running DxDiag with "dontskip" command line parameter or choosing not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Sound Tab 3: No problems found. Sound Tab 4: No problems found. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: NVIDIA GeForce GTX 1060 3GB Manufacturer: NVIDIA Chip type: NVIDIA GeForce GTX 1060 3GB DAC type: Integrated RAMDAC Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_10DE&DEV_1C02&SUBSYS_85B11043&REV_A1 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 11135 MB Dedicated Memory: 2988 MB Shared Memory: 8147 MB Current Mode: 1920 x 1080 (32 bit) (144Hz) HDR Support: Not Supported Display Topology: Internal Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.654297,0.333008), Green(0.324219,0.625000), Blue(0.157227,0.075195), White Point(0.312500,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: 2590G4 Monitor Id: AOC2590 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: Displayport External Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumdx.dll Driver File Version: 30.00.0015.1165 (English) Driver Version: 30.0.15.1165 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.7 Hardware Scheduling: Supported:True Enabled:False Graphics Preemption: Pixel Compute Preemption: Dispatch Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Not Supported Power P-states: Not Supported Virtualization: Paravirtualization Block List: No Blocks Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 28/01/2022 02:00:00, 1057368 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B71E3E-5F42-11CF-7E77-BEA50EC2D335} Vendor ID: 0x10DE Device ID: 0x1C02 SubSys ID: 0x85B11043 Revision ID: 0x00A1 Driver Strong Name: oem26.inf:0f066de38c1dbfb9:Section025:30.0.15.1165:pci\ven_10de&dev_1c02 Rank Of Driver: 00CF2001 Video Accel: DXVA2 Modes: {86695F12-340E-4F04-9FD3-9253DD327460} DXVA2_ModeMPEG2_VLD {6F3EC719-3735-42CC-8063-65CC3CB36616} DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD {32FCFE3F-DE46-4A49-861B-AC71110649D5} DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 {20BB8B0A-97AA-4571-8E99-64E60606C1A6} {15DF9B21-06C4-47F1-841E-A67C97D7F312} DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC {9947EC6F-689B-11DC-A320-0019DBBC4184} {33FCFE41-DE46-4A49-861B-AC71110649D5} DXVA2_ModeVP9_VLD_Profile0 {6AFFD11E-1D96-42B1-A215-93A31F09A53D} {914C84A3-4078-4FA9-984C-E2F262CB5C9C} Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Not Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 1 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported ------------- Sound Devices ------------- Description: 2590G4 (3- NVIDIA High Definition Audio) Default Sound Playback: Yes Default Voice Playback: No Hardware ID: HDAUDIO\FUNC_01&VEN_10DE&DEV_0084&SUBSYS_104385B1&REV_1001 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: nvhda64v.sys Driver Version: 1.3.38.16 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 24/07/2019 02:00:00, 237424 bytes Other Files: Driver Provider: NVIDIA Corporation HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No Description: Speakers (2- USB Audio CODEC ) Default Sound Playback: No Default Voice Playback: Yes Hardware ID: USB\VID_08BB&PID_2902&REV_0100&MI_00 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: USBAUDIO.sys Driver Version: 10.0.19041.1202 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 26/08/2021 02:00:00, 209920 bytes Other Files: Driver Provider: Microsoft HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No Description: Speakers (PRO X) Default Sound Playback: No Default Voice Playback: No Hardware ID: USB\VID_046D&PID_0AAA&REV_0031&MI_00 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: USBAUDIO.sys Driver Version: 10.0.19041.1202 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 26/08/2021 02:00:00, 209920 bytes Other Files: Driver Provider: Microsoft HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No Description: Speakers (Realtek High Definition Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0B00&SUBSYS_18491204&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: RTKVHD64.sys Driver Version: 6.0.9136.1 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 23/03/2021 02:00:00, 6446616 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- Description: Microphone (2- USB Audio CODEC ) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: USBAUDIO.sys Driver Version: 10.0.19041.1202 (English) Driver Attributes: Final Retail Date and Size: 26/08/2021 02:00:00, 209920 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF Description: Microphone (PRO X) Default Sound Capture: No Default Voice Capture: No Driver Name: USBAUDIO.sys Driver Version: 10.0.19041.1202 (English) Driver Attributes: Final Retail Date and Size: 26/08/2021 02:00:00, 209920 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 0 --------------------- ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: PRO X Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0x0AAA FF Driver: n/a Device Name: USB Audio CODEC Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x08BB, 0x2902 FF Driver: n/a Device Name: USB Gaming Mouse Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04D9, 0xAD50 FF Driver: n/a Device Name: USB Gaming Mouse Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04D9, 0xAD50 FF Driver: n/a Device Name: USB Gaming Mouse Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04D9, 0xAD50 FF Driver: n/a Device Name: USB-HID Gaming Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x1EA7, 0x0907 FF Driver: n/a Device Name: USB-HID Gaming Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x1EA7, 0x0907 FF Driver: n/a Device Name: USB Gaming Mouse Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04D9, 0xAD50 FF Driver: n/a Device Name: USB-HID Gaming Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x1EA7, 0x0907 FF Driver: n/a Device Name: PRO X Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0x0AAA FF Driver: n/a Device Name: PRO X Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0x0AAA FF Driver: n/a Device Name: PRO X Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0x0AAA FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x06ED | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 9/25/2021 11:57:47, 648016 bytes | +-+ USB Composite Device | | Vendor/Product ID: 0x04D9, 0xAD50 | | Location: Port_#0003.Hub_#0001 | | Matching Device ID: USB\COMPOSITE | | Service: usbccgp | | Driver: usbccgp.sys, 4/9/2021 15:48:54, 185664 bytes | | | +-+ USB Input Device | | | Vendor/Product ID: 0x04D9, 0xAD50 | | | Location: 0000.0014.0000.003.000.000.000.000.000 | | | Matching Device ID: USB\Class_03&SubClass_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 4/9/2021 15:48:54, 44032 bytes | | | Driver: hidclass.sys, 4/9/2021 15:48:54, 225792 bytes | | | Driver: hidparse.sys, 4/9/2021 15:48:54, 46080 bytes | | | | | +-+ HID-compliant mouse | | | | Vendor/Product ID: 0x04D9, 0xAD50 | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | Service: mouhid | | | | Driver: mouhid.sys, 12/7/2019 11:07:56, 35328 bytes | | | | Driver: mouclass.sys, 12/7/2019 11:07:56, 67600 bytes | | | | +-+ USB Input Device | | | Vendor/Product ID: 0x04D9, 0xAD50 | | | Location: 0000.0014.0000.003.000.000.000.000.000 | | | Matching Device ID: USB\Class_03 | | | Service: HidUsb | | | Driver: hidusb.sys, 4/9/2021 15:48:54, 44032 bytes | | | Driver: hidclass.sys, 4/9/2021 15:48:54, 225792 bytes | | | Driver: hidparse.sys, 4/9/2021 15:48:54, 46080 bytes | | | | | +-+ HID Keyboard Device | | | | Vendor/Product ID: 0x04D9, 0xAD50 | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | Service: kbdhid | | | | Driver: kbdhid.sys, 12/7/2019 11:07:56, 46592 bytes | | | | Driver: kbdclass.sys, 12/7/2019 11:07:56, 71480 bytes | | | | | | +-+ HID-compliant mouse | | | | Vendor/Product ID: 0x04D9, 0xAD50 | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | Service: mouhid | | | | Driver: mouhid.sys, 12/7/2019 11:07:56, 35328 bytes | | | | Driver: mouclass.sys, 12/7/2019 11:07:56, 67600 bytes | | +-+ USB Composite Device | | Vendor/Product ID: 0x1EA7, 0x0907 | | Location: Port_#0006.Hub_#0001 | | Matching Device ID: USB\COMPOSITE | | Service: usbccgp | | Driver: usbccgp.sys, 4/9/2021 15:48:54, 185664 bytes | | | +-+ USB Input Device | | | Vendor/Product ID: 0x1EA7, 0x0907 | | | Location: 0000.0014.0000.006.000.000.000.000.000 | | | Matching Device ID: USB\Class_03&SubClass_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 4/9/2021 15:48:54, 44032 bytes | | | Driver: hidclass.sys, 4/9/2021 15:48:54, 225792 bytes | | | Driver: hidparse.sys, 4/9/2021 15:48:54, 46080 bytes | | | | | +-+ HID Keyboard Device | | | | Vendor/Product ID: 0x1EA7, 0x0907 | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | Service: kbdhid | | | | Driver: kbdhid.sys, 12/7/2019 11:07:56, 46592 bytes | | | | Driver: kbdclass.sys, 12/7/2019 11:07:56, 71480 bytes | | | | +-+ USB Input Device | | | Vendor/Product ID: 0x1EA7, 0x0907 | | | Location: 0000.0014.0000.006.000.000.000.000.000 | | | Matching Device ID: USB\Class_03 | | | Service: HidUsb | | | Driver: hidusb.sys, 4/9/2021 15:48:54, 44032 bytes | | | Driver: hidclass.sys, 4/9/2021 15:48:54, 225792 bytes | | | Driver: hidparse.sys, 4/9/2021 15:48:54, 46080 bytes | | | | | +-+ HID Keyboard Device | | | | Vendor/Product ID: 0x1EA7, 0x0907 | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | Service: kbdhid | | | | Driver: kbdhid.sys, 12/7/2019 11:07:56, 46592 bytes | | | | Driver: kbdclass.sys, 12/7/2019 11:07:56, 71480 bytes | | | | | | +-+ HID-compliant mouse | | | | Vendor/Product ID: 0x1EA7, 0x0907 | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | Service: mouhid | | | | Driver: mouhid.sys, 12/7/2019 11:07:56, 35328 bytes | | | | Driver: mouclass.sys, 12/7/2019 11:07:56, 67600 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ -------------- System Devices -------------- Name: Intel(R) PCI Express Root Port #4 - 06BB Device ID: PCI\VEN_8086&DEV_06BB&SUBSYS_06BB1849&REV_F0\3&11583659&0&E3 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/17/2021 13:49:34, 469840 bytes Name: Intel(R) PCI Express Root Port #21 - 06AC Device ID: PCI\VEN_8086&DEV_06AC&SUBSYS_06AC1849&REV_F0\3&11583659&0&D8 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/17/2021 13:49:34, 469840 bytes Name: Realtek Gaming 2.5GbE Family Controller Device ID: PCI\VEN_10EC&DEV_8125&SUBSYS_81681849&REV_05\4&32AC88EE&0&00E3 Driver: C:\Windows\system32\DRIVERS\rt640x64.sys, 10.46.1231.2020 (English), 8/17/2021 19:08:32, 1147384 bytes Name: Standard SATA AHCI Controller Device ID: PCI\VEN_8086&DEV_06D2&SUBSYS_06D21849&REV_00\3&11583659&0&B8 Driver: C:\Windows\system32\DRIVERS\storahci.sys, 10.00.19041.1288 (English), 10/15/2021 08:22:00, 186168 bytes Name: Intel(R) SPI (flash) Controller - 06A4 Device ID: PCI\VEN_8086&DEV_06A4&SUBSYS_06A41849&REV_00\3&11583659&0&FD Driver: n/a Name: Intel(R) Thermal Subsystem - 06F9 Device ID: PCI\VEN_8086&DEV_06F9&SUBSYS_06F91849&REV_00\3&11583659&0&90 Driver: n/a Name: PCI standard host CPU bridge Device ID: PCI\VEN_8086&DEV_9B33&SUBSYS_9B331849&REV_05\3&11583659&0&00 Driver: n/a Name: Intel(R) Shared SRAM - 06EF Device ID: PCI\VEN_8086&DEV_06EF&SUBSYS_06EF1849&REV_00\3&11583659&0&A2 Driver: n/a Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_06ED&SUBSYS_06ED1849&REV_00\3&11583659&0&A0 Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.1503 (English), 2/9/2022 12:24:54, 629048 bytes Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.1503 (English), 2/9/2022 12:24:54, 137920 bytes Name: Intel(R) PCI Express Root Port #3 - 06BA Device ID: PCI\VEN_8086&DEV_06BA&SUBSYS_06BA1849&REV_F0\3&11583659&0&E0 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/17/2021 13:49:34, 469840 bytes Name: Standard NVM Express Controller Device ID: PCI\VEN_1987&DEV_5012&SUBSYS_50121987&REV_01\4&2BBD1BB3&0&00D8 Driver: C:\Windows\system32\DRIVERS\stornvme.sys, 10.00.19041.1266 (English), 10/15/2021 08:22:00, 158008 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1901&SUBSYS_19011849&REV_05\3&11583659&0&08 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/17/2021 13:49:34, 469840 bytes Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_06E0&SUBSYS_06E01849&REV_00\3&11583659&0&B0 Driver: C:\Windows\System32\DriverStore\FileRepository\heci.inf_amd64_c22251d5ea82b3c3\x64\TeeDriverW10x64.sys, 2131.01.0004.0000 (English), 8/19/2021 05:30:18, 309384 bytes Name: High Definition Audio Controller Device ID: PCI\VEN_10DE&DEV_10F1&SUBSYS_85B11043&REV_A1\4&30760922&0&0108 Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 10.00.19041.1081 (English), 9/25/2021 11:57:46, 139776 bytes Driver: C:\Windows\system32\DRIVERS\drmk.sys, 10.00.19041.0746 (English), 4/9/2021 15:48:53, 97792 bytes Driver: C:\Windows\system32\DRIVERS\portcls.sys, 10.00.19041.0746 (English), 4/9/2021 15:48:54, 388608 bytes Name: NVIDIA GeForce GTX 1060 3GB Device ID: PCI\VEN_10DE&DEV_1C02&SUBSYS_85B11043&REV_A1\4&30760922&0&0008 Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NVWMI\nvPerfProvider.man, 1/28/2022 13:28:54, 14175 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NVWMI\nvWmi.mof, 1/28/2022 13:28:54, 148921 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NVWMI\nvWmi64.exe, 2.36.0000.0000 (English), 1/28/2022 21:20:36, 4478912 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\MessageBus.dll, 1.22.2758.1620 (English), 1/28/2022 21:19:38, 7535584 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\NVDisplay.Container.exe, 1.35.3033.8148 (English), 1/28/2022 21:19:40, 1021408 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\NvContainerRecovery.bat, 1/28/2022 13:28:54, 1951 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\dlsargs.xml, 1/28/2022 13:28:54, 544 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\dlsnetparams.csv, 1/28/2022 13:28:54, 1191192 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\messagebus_client.conf, 1/28/2022 13:28:54, 57 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\nvgwls.exe, 1/28/2022 21:19:42, 33230816 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\nvtopps.db3, 1/28/2022 13:28:54, 122880 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\LocalSystem\NvXDCore.dll, 30.00.0015.1165 (English), 1/28/2022 21:19:48, 1844392 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\LocalSystem\NvcDispCorePlugin.dll, 30.00.0015.1165 (English), 1/28/2022 21:19:44, 523704 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\LocalSystem\NvcDispWatchdog.dll, 1.34.3030.7627 (English), 1/28/2022 21:19:48, 745432 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\LocalSystem\_DisplayDriverRAS.dll, 1.10.0000.0000 (English), 1/28/2022 21:19:52, 2618536 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\LocalSystem\_NvMsgBusBroadcast.dll, 1.34.3030.7627 (English), 1/28/2022 21:19:56, 3190200 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\LocalSystem\messagebus.conf, 1/28/2022 13:28:54, 57 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\LocalSystem\wksServicePluginZ.dll, 30.00.0015.1165 (English), 1/28/2022 21:19:52, 1238144 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\Session\NvFBCPlugin.dll, 6.14.0015.1165 (English), 1/28/2022 21:19:56, 1381544 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\Session\_nvppo.dll, 30.00.0015.1165 (English), 1/28/2022 21:20:04, 1608872 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\Session\_nvtopps.dll, 30.00.0015.1165 (English), 1/28/2022 21:20:06, 14261416 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\Session\nvprofileupdaterplugin.dll, 30.00.0015.1165 (English), 1/28/2022 21:19:58, 2193576 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\Session\nvxdsyncplugin.dll, 8.17.0015.1165 (English), 1/28/2022 21:20:00, 1815720 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\Display.NvContainer\plugins\Session\wksServicePlugin.dll, 30.00.0015.1165 (English), 1/28/2022 21:20:02, 624096 bytes Driver: C:\Windows\system32\DRIVERS\NVIDIA Corporation\Drs\dbInstaller.exe, 30.00.0015.1165 (English), 1/28/2022 21:13:00, 729232 bytes Driver: C:\Windows\system32\DRIVERS\NVIDIA Corporation\Drs\nvdrsdb.bin, 1/28/2022 13:28:54, 1824200 bytes Driver: C:\Windows\system32\nvcpl.dll, 8.17.0015.1165 (English), 1/28/2022 21:14:34, 5726336 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nv3dappshext.dll, 6.14.0015.1165 (English), 1/28/2022 21:13:22, 1001912 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nv3dappshextr.dll, 6.14.0015.1165 (English), 1/28/2022 21:13:24, 93112 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvcoproc.bin, 1/28/2022 13:28:54, 9919167 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvcpl.dll, 8.17.0015.1165 (English), 1/28/2022 21:14:34, 5726336 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvdevtools.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:10, 4545152 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvdevtoolsr.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:12, 232576 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvdisps.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:14, 11602048 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvdispsr.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:16, 11320248 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvgames.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:38, 12361360 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvgamesr.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:40, 12646032 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvlicensings.dll, 6.14.0015.1165 (English), 1/28/2022 21:16:22, 4550616 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvlicensingsr.dll, 6.14.0015.1165 (English), 1/28/2022 21:16:24, 295352 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvshext.dll, 1.02.0000.0001 (English), 1/28/2022 21:18:10, 129152 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvsmartmax.dll, 6.14.0010.10003 (English), 1/28/2022 21:18:12, 203904 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvsmartmax64.dll, 6.14.0010.10003 (English), 1/28/2022 21:18:14, 245176 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvsmartmaxapp.exe, 6.14.0010.10003 (English), 1/28/2022 21:18:16, 275384 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvsmartmaxapp64.exe, 6.14.0010.10003 (English), 1/28/2022 21:18:16, 285624 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvsvc64.dll, 30.00.0015.1165 (English), 1/28/2022 21:18:18, 2651264 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvsvcr.dll, 30.00.0015.1165 (English), 1/28/2022 21:18:22, 1768888 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvsvs.dll, 30.00.0015.1165 (English), 1/28/2022 21:18:22, 5061248 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvsvsr.dll, 30.00.0015.1165 (English), 1/28/2022 21:18:26, 1948088 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvui.dll, 8.17.0015.1165 (English), 1/28/2022 21:18:30, 6641080 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvuir.dll, 8.17.0015.1165 (English), 1/28/2022 21:18:32, 2613176 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvvitvs.dll, 30.00.0015.1165 (English), 1/28/2022 21:18:40, 7407248 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvvitvsr.dll, 30.00.0015.1165 (English), 1/28/2022 21:18:42, 4114880 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvwss.dll, 30.00.0015.1165 (English), 1/28/2022 21:18:52, 12210144 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvwssr.dll, 30.00.0015.1165 (English), 1/28/2022 21:18:56, 9360040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvxdapix.dll, 8.17.0015.1165 (English), 1/28/2022 21:19:02, 9339024 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvxdbat.dll, 8.17.0015.1165 (English), 1/28/2022 21:19:06, 1623488 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvxdplcy.dll, 8.17.0015.1165 (English), 1/28/2022 21:19:08, 1876928 bytes Driver: C:\Windows\system32\lxss\lib\libcuda.so, 1/28/2022 13:28:54, 137240 bytes Driver: C:\Windows\system32\lxss\lib\libcuda.so.1, 1/28/2022 13:28:54, 137240 bytes Driver: C:\Windows\system32\lxss\lib\libcuda.so.1.1, 1/28/2022 13:28:54, 137240 bytes Driver: C:\Windows\system32\lxss\lib\libnvcuvid.so, 1/28/2022 13:28:54, 5864608 bytes Driver: C:\Windows\system32\lxss\lib\libnvcuvid.so.1, 1/28/2022 13:28:54, 5864608 bytes Driver: C:\Windows\system32\lxss\lib\libnvdxdlkernels.so, 1/28/2022 13:28:54, 35512144 bytes Driver: C:\Windows\system32\lxss\lib\libnvidia-encode.so, 1/28/2022 13:28:54, 424400 bytes Driver: C:\Windows\system32\lxss\lib\libnvidia-encode.so.1, 1/28/2022 13:28:54, 424400 bytes Driver: C:\Windows\system32\lxss\lib\libnvidia-ml.so.1, 1/28/2022 13:28:54, 207360 bytes Driver: C:\Windows\system32\lxss\lib\libnvidia-opticalflow.so, 1/28/2022 13:28:54, 354768 bytes Driver: C:\Windows\system32\lxss\lib\libnvidia-opticalflow.so.1, 1/28/2022 13:28:54, 354768 bytes Driver: C:\Windows\system32\lxss\lib\libnvwgf2umx.so, 1/28/2022 13:28:54, 45918760 bytes Driver: C:\Windows\system32\lxss\lib\nvidia-smi, 1/28/2022 13:28:54, 690808 bytes Driver: C:\Windows\system32\DRIVERS\NVIDIA Corporation\license.txt, 1/28/2022 13:28:54, 28827 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\FreqTransfer32.exe, 1/28/2022 21:20:12, 3703952 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\FreqTransfer64.exe, 1/28/2022 21:20:14, 4004520 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\GreenScreenBG01.jpg, 1/28/2022 13:28:54, 281528 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\GreenScreenBG02.jpg, 1/28/2022 13:28:54, 499736 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\HighresBlender32.exe, 1/28/2022 21:20:14, 3811472 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\HighresBlender64.exe, 1/28/2022 21:20:16, 4109248 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\NvCamera32.dll, 7.01.0797.0808 (English), 1/28/2022 21:20:18, 8042664 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\NvCamera64.dll, 7.01.0797.0808 (English), 1/28/2022 21:20:20, 8544400 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\NvCameraAllowlisting32.dll, 7.01.0797.0808 (English), 1/28/2022 21:20:22, 561120 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\NvCameraAllowlisting64.dll, 7.01.0797.0808 (English), 1/28/2022 21:20:24, 705984 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\NvCameraEnable.exe, 1/28/2022 21:20:26, 373728 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\NvImageConvert32.exe, 1/28/2022 21:20:26, 3708888 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\NvImageConvert64.exe, 1/28/2022 21:20:28, 3986576 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\ReShadeFXC32.exe, 2.00.0000.0000 (English), 1/28/2022 21:20:30, 775104 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\ReShadeFXC64.exe, 2.00.0000.0000 (English), 1/28/2022 21:20:30, 890840 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\ShotWithGeforce518x32.rgba, 1/28/2022 13:28:54, 66304 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\SphericalEquirect32.exe, 1/28/2022 21:20:32, 3675816 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\SphericalEquirect64.exe, 1/28/2022 21:20:34, 3923088 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\Sticker01.png, 1/28/2022 13:28:54, 49695 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\Sticker02.png, 1/28/2022 13:28:54, 474002 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\Sticker03.png, 1/28/2022 13:28:54, 380006 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\Sticker04.png, 1/28/2022 13:28:54, 86881 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\Sticker05.png, 1/28/2022 13:28:54, 59304 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\Sticker06.png, 1/28/2022 13:28:54, 13547 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\Sticker07.png, 1/28/2022 13:28:54, 6342 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\Sticker08.png, 1/28/2022 13:28:54, 96493 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\d3dcompiler_47_32.dll, 6.03.9600.16384 (English), 1/28/2022 21:20:08, 3469784 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\d3dcompiler_47_64.dll, 6.03.9600.16384 (English), 1/28/2022 21:20:10, 4175800 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\scratches.jpg, 1/28/2022 13:28:54, 346354 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\tools_licenses.txt, 1/28/2022 13:28:54, 15970 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvCamera\ui.tga, 1/28/2022 13:28:54, 120236 bytes Driver: C:\Windows\system32\MCU.exe, 1.01.5204.20580 (English), 1/28/2022 21:13:20, 850872 bytes Driver: C:\Windows\system32\nvdebugdump.exe, 6.14.0015.1165 (English), 1/28/2022 21:15:04, 455808 bytes Driver: C:\Windows\system32\nvidia-smi.exe, 8.17.0015.1165 (English), 1/28/2022 21:15:50, 710800 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvopencl32.dll, 30.00.0015.1165 (English), 1/28/2022 21:17:06, 16295360 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvopencl64.dll, 30.00.0015.1165 (English), 1/28/2022 21:17:14, 18971304 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvcompiler32.dll, 30.00.0015.1165 (English), 1/28/2022 21:13:32, 41485440 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvcompiler64.dll, 30.00.0015.1165 (English), 1/28/2022 21:13:48, 46249912 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvcompilernext32.dll, 30.00.0015.1165 (English), 1/28/2022 21:14:00, 60178360 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvcompilernext64.dll, 30.00.0015.1165 (English), 1/28/2022 21:14:18, 67797424 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvlddmkm.sys, 30.00.0015.1165 (English), 1/28/2022 21:16:14, 42281128 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libcuda.so.1.1, 1/28/2022 13:28:54, 22555496 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libcuda_loader.so, 1/28/2022 13:28:54, 137240 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libnvcuvid.so.1, 1/28/2022 13:28:54, 5864608 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libnvdxdlkernels.so, 1/28/2022 13:28:54, 35512144 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libnvidia-encode.so.1, 1/28/2022 13:28:54, 424400 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libnvidia-ml.so.1, 1/28/2022 13:28:54, 1869112 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libnvidia-ml_loader.so, 1/28/2022 13:28:54, 207360 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libnvidia-nvvm.so, 1/28/2022 13:28:54, 26941176 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libnvidia-opticalflow.so.1, 1/28/2022 13:28:54, 354768 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libnvidia-ptxjitcompiler.so.1, 1/28/2022 13:28:54, 11419032 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\libnvwgf2umx.so, 1/28/2022 13:28:54, 45918760 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nv-vk64.json, 1/28/2022 13:28:54, 671 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvDecMFTMjpeg.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:06, 639416 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvDecMFTMjpegx.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:08, 812672 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvEncMFTH264.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:22, 1172920 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvEncMFTH264x.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:24, 1458320 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvEncMFThevc.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:26, 1176720 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvEncMFThevcx.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:28, 1471632 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvcuda32.dll, 30.00.0015.1165 (English), 1/28/2022 21:14:36, 20417472 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvcuda64.dll, 30.00.0015.1165 (English), 1/28/2022 21:14:44, 23580096 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvd3dumx.dll, 30.00.0015.1165 (English), 1/28/2022 21:11:48, 24974672 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvd3dumx_cfg.dll, 30.00.0015.1165 (English), 1/28/2022 21:11:56, 25218848 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvdlistx.dll, 30.00.0015.1165 (English), 1/28/2022 21:12:12, 216136 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvdxdlkernels.dll, 1/28/2022 21:15:22, 35818624 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvidia-smi, 1/28/2022 13:28:54, 690808 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumdx.dll, 30.00.0015.1165 (English), 1/28/2022 21:12:16, 1057368 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvml.dll, 8.17.0015.1165 (English), 1/28/2022 21:16:26, 1166464 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvoglv64.dll, 30.00.0015.1165 (English), 1/28/2022 21:16:52, 49778616 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvoptix.bin, 1/28/2022 13:28:54, 133668492 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvoptix.dll, 7.04.0001.0000 (English), 1/28/2022 21:17:24, 43129488 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvptxJitCompiler32.dll, 30.00.0015.1165 (English), 1/28/2022 21:17:40, 7976928 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvptxJitCompiler64.dll, 30.00.0015.1165 (English), 1/28/2022 21:17:44, 9100456 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvrtum64.dll, 30.00.0015.1165 (English), 1/28/2022 21:17:50, 72649176 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvvm64_40_0.dll, 6.14.0011.9000 (English), 1/28/2022 21:18:44, 17957008 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvwgf2umx.dll, 30.00.0015.1165 (English), 1/28/2022 21:12:32, 43264160 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvwgf2umx_cfg.dll, 30.00.0015.1165 (English), 1/28/2022 21:12:44, 43675480 bytes Driver: C:\Windows\system32\NvFBC64.dll, 6.14.0015.1165 (English), 1/28/2022 21:15:36, 2121360 bytes Driver: C:\Windows\system32\NvIFR64.dll, 6.14.0015.1165 (English), 1/28/2022 21:16:08, 1528448 bytes Driver: C:\Windows\system32\OpenCL.dll, 3.00.0001.0000 (English), 1/28/2022 21:19:22, 1466000 bytes Driver: C:\Windows\system32\nvEncodeAPI64.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:32, 985024 bytes Driver: C:\Windows\system32\nvapi64.dll, 30.00.0015.1165 (English), 1/28/2022 21:11:36, 7612320 bytes Driver: C:\Windows\system32\nvcuda.dll, 30.00.0015.1165 (English), 1/28/2022 21:14:54, 2932864 bytes Driver: C:\Windows\system32\nvcuvid.dll, 7.17.0015.1165 (English), 1/28/2022 21:15:00, 8610432 bytes Driver: C:\Windows\system32\nvinfo.pb, 1/28/2022 13:28:54, 89185 bytes Driver: C:\Windows\system32\nvml.dll, 8.17.0015.1165 (English), 1/28/2022 21:16:26, 714880 bytes Driver: C:\Windows\system32\nvofapi64.dll, 1/28/2022 21:16:38, 795264 bytes Driver: C:\Windows\system32\vulkan-1-999-0-0-0.dll, 1.03.0198.0001 (English), 1/28/2022 21:19:28, 1432312 bytes Driver: C:\Windows\system32\vulkan-1.dll, 1.03.0198.0001 (English), 1/28/2022 21:19:28, 1432312 bytes Driver: C:\Windows\system32\vulkaninfo-1-999-0-0-0.exe, 1.03.0198.0001 (English), 1/28/2022 21:19:32, 1905936 bytes Driver: C:\Windows\system32\vulkaninfo.exe, 1.03.0198.0001 (English), 1/28/2022 21:19:32, 1905936 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nv-vk32.json, 1/28/2022 13:28:54, 671 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvIccAdvancedColorIdentity.icm, 1/28/2022 13:28:54, 3288 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvd3dum.dll, 30.00.0015.1165 (English), 1/28/2022 21:11:40, 21251304 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvd3dum_cfg.dll, 30.00.0015.1165 (English), 1/28/2022 21:12:06, 21655440 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvdispco64.exe, 1.00.0016.0000 (English), 1/28/2022 21:15:14, 1550464 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvdlist.dll, 30.00.0015.1165 (English), 1/28/2022 21:12:12, 181808 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvldumd.dll, 30.00.0015.1165 (English), 1/28/2022 21:12:14, 881160 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvoglv32.dll, 30.00.0015.1165 (English), 1/28/2022 21:16:40, 36473272 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvwgf2um.dll, 30.00.0015.1165 (English), 1/28/2022 21:12:20, 35306896 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvwgf2um_cfg.dll, 30.00.0015.1165 (English), 1/28/2022 21:12:58, 35921472 bytes Driver: C:\Windows\SysWow64\NvFBC.dll, 6.14.0015.1165 (English), 1/28/2022 21:15:34, 1602704 bytes Driver: C:\Windows\SysWow64\NvIFR.dll, 6.14.0015.1165 (English), 1/28/2022 21:16:06, 1179584 bytes Driver: C:\Windows\SysWow64\OpenCL.dll, 3.00.0001.0000 (English), 1/28/2022 21:19:20, 1207440 bytes Driver: C:\Windows\SysWow64\nvEncodeAPI.dll, 30.00.0015.1165 (English), 1/28/2022 21:15:30, 794552 bytes Driver: C:\Windows\SysWow64\nvapi.dll, 30.00.0015.1165 (English), 1/28/2022 21:11:32, 6459952 bytes Driver: C:\Windows\SysWow64\nvcuda.dll, 30.00.0015.1165 (English), 1/28/2022 21:14:52, 5098112 bytes Driver: C:\Windows\SysWow64\nvcuvid.dll, 7.17.0015.1165 (English), 1/28/2022 21:14:56, 7715256 bytes Driver: C:\Windows\SysWow64\nvofapi.dll, 1/28/2022 21:16:36, 638912 bytes Driver: C:\Windows\SysWow64\vulkan-1-999-0-0-0.dll, 1.03.0198.0001 (English), 1/28/2022 21:19:30, 1144552 bytes Driver: C:\Windows\SysWow64\vulkan-1.dll, 1.03.0198.0001 (English), 1/28/2022 21:19:30, 1144552 bytes Driver: C:\Windows\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.03.0198.0001 (English), 1/28/2022 21:19:34, 1478416 bytes Driver: C:\Windows\SysWow64\vulkaninfo.exe, 1.03.0198.0001 (English), 1/28/2022 21:19:34, 1478416 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\NvTelemetry64.dll, 14.03.0060.0000 (English), 1/28/2022 21:18:28, 4466088 bytes Name: Intel(R) Ethernet Connection (11) I219-V Device ID: PCI\VEN_8086&DEV_0D4D&SUBSYS_0D4D1849&REV_00\3&11583659&0&FE Driver: C:\Windows\System32\DriverStore\FileRepository\e1d68x64.inf_amd64_d31d833ebd189f40\e1d68x64.sys, 12.19.0001.0035 (English), 1/19/2021 07:07:36, 601448 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\e1d68x64.inf_amd64_d31d833ebd189f40\e1dmsg.dll, 10.00.0935.0000 (English), 1/19/2021 07:07:38, 118648 bytes Name: High Definition Audio Controller Device ID: PCI\VEN_8086&DEV_06C8&SUBSYS_12041849&REV_00\3&11583659&0&FB Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 10.00.19041.1081 (English), 9/25/2021 11:57:46, 139776 bytes Driver: C:\Windows\system32\DRIVERS\drmk.sys, 10.00.19041.0746 (English), 4/9/2021 15:48:53, 97792 bytes Driver: C:\Windows\system32\DRIVERS\portcls.sys, 10.00.19041.0746 (English), 4/9/2021 15:48:54, 388608 bytes Name: Intel(R) SMBus - 06A3 Device ID: PCI\VEN_8086&DEV_06A3&SUBSYS_06A31849&REV_00\3&11583659&0&FC Driver: n/a Name: Intel(R) Dual Band Wireless-AC 3168 Device ID: PCI\VEN_8086&DEV_24FB&SUBSYS_21108086&REV_10\4&3B5BA214&0&00E0 Driver: C:\Windows\system32\DRIVERS\Netwtw04.sys, 19.51.0028.0001 (English), 2/6/2020 00:39:24, 8673040 bytes Driver: C:\Windows\system32\DRIVERS\Netwfw04.dat, 2/5/2020 20:27:06, 2074564 bytes Driver: C:\Windows\system32\IntelIHVRouter04.dll, 3.00.0000.0001 (English), 2/6/2020 00:39:24, 1086224 bytes Name: Intel(R) LPC Controller (Z490) - 0685 Device ID: PCI\VEN_8086&DEV_0685&SUBSYS_06851849&REV_00\3&11583659&0&F8 Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 10.00.19041.1202 (English), 9/25/2021 11:57:47, 20280 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.19041.1288 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.19041.1288 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.19041.0001 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.19041.0001 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.19041.0450 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.19041.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.19041.1110 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.19041.1165 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.19041.1165 DV Muxer,0x00400000,0,0,qdv.dll,10.00.19041.0001 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.19041.0746 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.19041.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.19041.0746 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.19041.0746 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.19041.1526 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.19041.0329 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.19041.0001 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.0746 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.19041.0746 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.0746 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.19041.0329 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.19041.0001 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.0001 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.19041.0746 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.19041.0746 DV Splitter,0x00600000,1,2,qdv.dll,10.00.19041.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.19041.0746 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.19041.0001 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.19041.0746 Video Renderer,0x00800001,1,0,quartz.dll,10.00.19041.0746 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.19041.0001 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.19041.0746 Video Renderer,0x00400000,1,0,quartz.dll,10.00.19041.0746 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.19041.0001 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.19041.0001 VEGAS Wave Hammer Surround,0x00200000,1,1,mchammer_x64.dll,1.01.0000.2477 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax, File writer,0x00200000,1,0,qcap.dll,10.00.19041.0001 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.19041.0746 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.19041.0746 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.0001 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.19041.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.19041.0329 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.19041.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.19041.0746 Null Renderer,0x00200000,1,0,qedit.dll,10.00.19041.0746 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.19041.0001 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.19041.0001 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.19041.0001 Smart Tee,0x00200000,1,2,qcap.dll,10.00.19041.0001 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.0746 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.19041.0746 Wave Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 File stream renderer,0x00400000,1,1,quartz.dll,10.00.19041.0746 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.19041.0001 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.19041.0001 AVI Mux,0x00200000,1,0,qcap.dll,10.00.19041.0001 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.19041.0746 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.19041.0746 File Source (URL),0x00400000,0,1,quartz.dll,10.00.19041.0746 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.19041.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.19041.0546 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.19041.0001 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.19041.0746 VEGAS ExpressFX Chorus,0x00200000,1,1,sfxpfx2_x64.dll,1.01.0000.2477 VEGAS ExpressFX Delay,0x00200000,1,1,sfxpfx2_x64.dll,1.01.0000.2477 VEGAS ExpressFX Distortion,0x00200000,1,1,sfxpfx1_x64.dll,1.01.0000.2477 VEGAS ExpressFX Equalization,0x00200000,1,1,sfxpfx2_x64.dll,1.01.0000.2477 VEGAS ExpressFX Flange/Wah-Wah,0x00200000,1,1,sfxpfx1_x64.dll,1.01.0000.2477 VEGAS ExpressFX Amplitude Modulation,0x00200000,1,1,sfxpfx2_x64.dll,1.01.0000.2477 VEGAS ExpressFX Reverb,0x00200000,1,1,sfxpfx1_x64.dll,1.01.0000.2477 VEGAS ExpressFX Stutter,0x00200000,1,1,sfxpfx1_x64.dll,1.01.0000.2477 VEGAS ExpressFX Dynamics,0x00200000,1,1,sfxpfx3_x64.dll,1.01.0000.2477 VEGAS ExpressFX Graphic EQ,0x00200000,1,1,sfxpfx3_x64.dll,1.01.0000.2477 VEGAS ExpressFX Noise Gate,0x00200000,1,1,sfxpfx3_x64.dll,1.01.0000.2477 VEGAS ExpressFX Time Stretch,0x00200000,1,1,sfxpfx3_x64.dll,1.01.0000.2477 VEGAS ExpressFX Audio Restoration,0x00200000,1,1,xpvinyl_x64.dll,1.01.0000.2477 VEGAS Multi-Band Dynamics,0x00200000,1,1,sfppack2_x64.dll,1.01.0000.2477 VEGAS Track Compressor,0x00200000,1,1,sftrkfx1_x64.dll,1.01.0000.2477 VEGAS Dither,0x00200000,1,1,sftrkfx1_x64.dll,1.01.0000.2477 VEGAS Chorus,0x00200000,1,1,sfppack1_x64.dll,1.01.0000.2477 VEGAS Distortion,0x00200000,1,1,sfppack3_x64.dll,1.01.0000.2477 VEGAS Gapper/Snipper,0x00200000,1,1,sfppack3_x64.dll,1.01.0000.2477 VEGAS Simple Delay,0x00200000,1,1,sfppack1_x64.dll,1.01.0000.2477 VEGAS Reverb,0x00200000,1,1,sfppack1_x64.dll,1.01.0000.2477 VEGAS Multi-Tap Delay,0x00200000,1,1,sfppack1_x64.dll,1.01.0000.2477 VEGAS Track Noise Gate,0x00200000,1,1,sftrkfx1_x64.dll,1.01.0000.2477 VEGAS Graphic EQ,0x00200000,1,1,sfppack2_x64.dll,1.01.0000.2477 VEGAS Track EQ,0x00200000,1,1,sftrkfx1_x64.dll,1.01.0000.2477 VEGAS Smooth/Enhance,0x00200000,1,1,sfppack3_x64.dll,1.01.0000.2477 VEGAS Resonant Filter,0x00200000,1,1,sfresfilter_x64.dll,1.01.0000.2477 VEGAS Parametric EQ,0x00200000,1,1,sfppack2_x64.dll,1.01.0000.2477 VEGAS Time Stretch,0x00200000,1,1,sfppack1_x64.dll,1.01.0000.2477 VEGAS Noise Gate,0x00200000,1,1,sfppack2_x64.dll,1.01.0000.2477 VEGAS Paragraphic EQ,0x00200000,1,1,sfppack2_x64.dll,1.01.0000.2477 VEGAS Vibrato,0x00200000,1,1,sfppack3_x64.dll,1.01.0000.2477 VEGAS Pan,0x00200000,1,1,sffrgpnv_x64.dll,1.01.0000.2477 VEGAS Pitch Shift,0x00200000,1,1,sfppack1_x64.dll,1.01.0000.2477 VEGAS Volume,0x00200000,1,1,sffrgpnv_x64.dll,1.01.0000.2477 VEGAS Flange/Wah-wah,0x00200000,1,1,sfppack3_x64.dll,1.01.0000.2477 VEGAS Graphic Dynamics,0x00200000,1,1,sfppack2_x64.dll,1.01.0000.2477 VEGAS Amplitude Modulation,0x00200000,1,1,sfppack3_x64.dll,1.01.0000.2477 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.19041.0867 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.19041.0001 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.19041.0001 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.19041.0001 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.19041.0746 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.19041.0508 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.19041.0508 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.0746 PCM,0x00200000,1,1,quartz.dll,10.00.19041.0746 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.0746 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.19041.0746 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.19041.0746 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.19041.0746 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.19041.0746 Audio Capture Sources: Microphone (2- USB Audio CODEC ),0x00200000,0,0,qcap.dll,10.00.19041.0001 Microphone (PRO X),0x00200000,0,0,qcap.dll,10.00.19041.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.19041.1266 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.1266 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.1266 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.19041.0746 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.19041.0746 WDM Streaming Capture Devices: Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Realtek HD Audio Line input,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 ,0x00000000,0,0,, USB Audio CODEC ,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 PRO X,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 WDM Streaming Rendering Devices: PRO X,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 Realtek HD Audio output,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 ,0x00000000,0,0,, USB Audio CODEC ,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.19041.0001 Video Capture Sources: OBS Virtual Camera,0x00200000,0,1,obs-virtualcam-module64.dll,27.01.0001.0000 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.0746 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.19041.0001 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.19041.0001 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Audio Renderers: 2590G4 (3- NVIDIA High Definition Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.19041.0746 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.19041.0746 DirectSound: Speakers (PRO X),0x00200000,1,0,quartz.dll,10.00.19041.0746 DirectSound: 2590G4 (3- NVIDIA High Definition Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746 DirectSound: Speakers (Realtek High Definition Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746 DirectSound: Speakers (2- USB Audio CODEC ),0x00200000,1,0,quartz.dll,10.00.19041.0746 Speakers (PRO X),0x00200000,1,0,quartz.dll,10.00.19041.0746 Speakers (Realtek High Definition Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746 Speakers (2- USB Audio CODEC ),0x00200000,1,0,quartz.dll,10.00.19041.0746 ---------------------------- Preferred DirectShow Filters ---------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred] , [, ] MEDIASUBTYPE_DVD_LPCM_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_VIDEO, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS {78766964-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_mp4s, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {64697678-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {58564944-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {5634504D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_MP4S, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject {44495658-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVA, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mpg4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_h264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_H264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_WMV3, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_MP43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMV2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS2, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_M4S2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WVP2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_WMV1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS1, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_WVC1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_AVC1, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_MPEG_LOAS, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG_ADTS_AAC, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_WMAUDIO_LOSSLESS, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_WMAUDIO3, WMAudio Decoder DMO, CLSID_CWMADecMediaObject WMMEDIASUBTYPE_WMAudioV8, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS WMMEDIASUBTYPE_MP3, MP3 Decoder DMO, CLSID_CMP3DecMediaObject MEDIASUBTYPE_MPEG1Payload, MPEG Video Decoder, CLSID_CMpegVideoCodec MEDIASUBTYPE_MPEG1Packet, MPEG Video Decoder, CLSID_CMpegVideoCodec {6C737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64687664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MJPG, MJPEG Decompressor, CLSID_MjpegDec {20637664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MPEG1AudioPayload, MPEG Audio Decoder, CLSID_CMpegAudioCodec WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject WMMEDIASUBTYPE_WMSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject --------------------------- Media Foundation File Versions --------------------------- mfcore.dll, 10.00.19041.1526 mfreadwrite.dll, 10.00.19041.0746 mfcaptureengine.dll, 10.00.19041.0906 mfsensorgroup.dll, 10.00.19041.1503 windows.media.dll, 10.00.19041.1387 frameserver.dll, 10.00.19041.1503 frameserverclient.dll, 10.00.19041.1503 --------------------------- Media Foundation Transforms --------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms] : , , , [, ], Video Decoders: Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 11.21.0002.0022 NVIDIA MJPEG Video Decoder MFT, {70F36578-2741-454F-B494-E8563DDD1CB4}, 0x4, 8, nvDecMFTMjpegx.dll, 30.00.0015.1165 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.19041.1526 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.19041.0001 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.19041.0450 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.19041.1526 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.19041.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.19041.1110 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.19041.1348 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.19041.1165 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.19041.1165 VP9VideoExtensionDecoder WebpImageExtension HEIFImageExtension Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 11.21.0002.0022 NVIDIA H.264 Encoder MFT, {60F44560-5A20-4857-BFEF-D29773CB8040}, 0x4, 8, nvEncMFTH264x.dll, 30.00.0015.1165 NVIDIA HEVC Encoder MFT, {966F107C-8EA2-425D-B822-E4A71BEF01D7}, 0x4, 8, nvEncMFThevcx.dll, 30.00.0015.1165 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 11.21.0002.0022 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.19041.1503 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.19041.0867 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.19041.0001 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.19041.0001 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.19041.0001 VP9VideoExtensionEncoder HEIFImageExtension Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.19041.0746 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.19041.0867 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.19041.0746 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.19041.0746 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.19041.1110 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.19041.1387 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.19041.1526 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.19041.0001 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.19041.1288 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.19041.1165 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.19041.1526 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.19041.1526 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.19041.1288 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.19041.0746 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.19041.1320 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.19041.1165 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.19041.0001 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.19041.1526 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.19041.1526 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.19041.0001 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.19041.0746 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.19041.1526 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.19041.0746 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.19041.0746 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.19041.0746 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.19041.1526 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.19041.0746 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.19041.0508 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.19041.0001 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.19041.0001 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.19041.0508 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.19041.0001 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.19041.0746 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.19041.0001 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.19041.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.19041.0001 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.19041.1503 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.19041.1526 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableDecoders = 1 EnableEncoders = 1 ------------------------------------- Media Foundation Byte Stream Handlers ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] .3g2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .ac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .adt, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .am?, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler .amr, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler, Preferred .asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred .dvr-ms, {A8721937-E2FB-4D7A-A9EE-4EB08C890B6E}, MF SBE Source ByteStreamHandler .dvr-ms, {65964407-A5D8-4060-85B0-1CCD63F768E2}, dvr-ms Byte Stream Handler, Preferred .ec3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred .m2t, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m2ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mk3d, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mka, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mks, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mkv, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mov, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp2v, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mpg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .nsc, {B084785C-DDE0-4D30-8CA8-05A373E185BE}, NSC Byte Stream Handler, Preferred .sami, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .smi, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .tod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .uvu, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .vob, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred .weba, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wtv, {65964407-A5D8-4060-85B0-1CCD63F768E2}, WTV Byte Stream Handler, Preferred audio/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/aacp, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/eac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/L16, {3FFB3B8C-EB99-472B-8902-E1C1B05F07CF}, LPCM Byte Stream Handler, Preferred audio/mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/MP4A-LATM, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/vnd.dlna.adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/vnd.dolby.dd-raw, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred audio/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred audio/x-aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/x-flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/x-m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred audio/x-mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-ms-wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred audio/x-wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred video/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/vnd.dece.mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/vnd.dlna.mpeg-tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred video/x-m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred video/x-ms-asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred -------------------------------- Media Foundation Scheme Handlers -------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] file:, {477EC299-1421-4BDD-971F-7CCB933F21AD}, File Scheme Handler, Preferred http:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler http:, {9EC4B4F9-3029-45AD-947B-344DE2A249E2}, Urlmon Scheme Handler http:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpd:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler, Preferred https:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpsd:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcast:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcrecv:, {FA6D33D4-9405-4BA5-9983-12604AC8E77A}, Miracast Sink Scheme Handler, Preferred mms:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ms-appdata:, {CFC81939-3886-4ACF-9692-DA58037AE716}, MsAppData Scheme Handler, Preferred ms-appx-web:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppxWeb Scheme Handler, Preferred ms-appx:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppx Scheme Handler, Preferred ms-winsoundevent:, {F79A6BF9-7415-4CF3-AE10-4559509ABC3C}, Sound Event Scheme Handler, Preferred rtsp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtsps:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred sdp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ------------------------------------- Preferred Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\Preferred] , [, ] {EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B} {E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {A61AC364-AD0E-4744-89FF-213CE0DF8804}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {63616C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905} MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9} {00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} {0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A} {00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} {00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_ADTS, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B} {00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC} {00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE} KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514} {00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786} KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD} WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject ------------------------------------- Disabled Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\DoNotUse] ------------------------ Disabled Media Sources ------------------------ [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse] --------------- EVR Power Information --------------- Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0 --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: Fault bucket 1371663545811212169, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: YouTube Music Desktop App.exe P2: 1.13.0.0 P3: 5f4dbeb4 P4: StackHash_fbea P5: 10.0.19041.1466 P6: e2f8ca76 P7: c0000374 P8: PCH_DD_FROM_ntdll+0x000000000009D8C4 P9: P10: +++ WER1 +++: Fault bucket 2219328941662607878, type 5 Event Name: FaultTolerantHeap Response: Not available Cab Id: 0 Problem signature: P1: YouTube Music Desktop App.exe P2: 1.13.0.0 P3: 5F4DBEB4 P4: ffffbaad P5: P6: P7: P8: P9: P10: +++ WER2 +++: Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 144 P2: 3003 P3: ffffc30f62def5b0 P4: 40010000 P5: 0 P6: 10_0_19043 P7: 0_0 P8: 256_1 P9: P10: +++ WER3 +++: Fault bucket , type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0 Problem signature: P1: 144 P2: 3003 P3: ffffc30f62def5b0 P4: 40010000 P5: 0 P6: 10_0_19043 P7: 0_0 P8: 256_1 P9: P10: +++ WER4 +++: Fault bucket 1840237190768174422, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: vgtray.exe P2: 1.11.2.112 P3: 61a58fcf P4: vgtray.exe P5: 1.11.2.112 P6: 61a58fcf P7: c0000005 P8: 0000000000072af4 P9: P10: +++ WER5 +++: Fault bucket 2219328941662607878, type 5 Event Name: FaultTolerantHeap Response: Not available Cab Id: 0 Problem signature: P1: YouTube Music Desktop App.exe P2: 1.13.0.0 P3: 5F4DBEB4 P4: ffffbaad P5: P6: P7: P8: P9: P10: +++ WER6 +++: Fault bucket 1371663545811212169, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: YouTube Music Desktop App.exe P2: 1.13.0.0 P3: 5f4dbeb4 P4: StackHash_fbea P5: 10.0.19041.1466 P6: e2f8ca76 P7: c0000374 P8: PCH_8B_FROM_ntdll+0x000000000009D8C4 P9: P10: +++ WER7 +++: Fault bucket 1840237190768174422, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: vgtray.exe P2: 1.11.2.112 P3: 61a58fcf P4: vgtray.exe P5: 1.11.2.112 P6: 61a58fcf P7: c0000005 P8: 0000000000072af4 P9: P10: +++ WER8 +++: Fault bucket 1840237190768174422, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: vgtray.exe P2: 1.11.2.112 P3: 61a58fcf P4: vgtray.exe P5: 1.11.2.112 P6: 61a58fcf P7: c0000005 P8: 0000000000072af4 P9: P10: +++ WER9 +++: Fault bucket 1371663545811212169, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: YouTube Music Desktop App.exe P2: 1.13.0.0 P3: 5f4dbeb4 P4: StackHash_fbea P5: 10.0.19041.1466 P6: e2f8ca76 P7: c0000374 P8: PCH_9F_FROM_ntdll+0x000000000009D8C4 P9: P10: ...#SSU#...