# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"05/13/2022" Time:"00:00:44.6830119" # Scanned Hardware Computer: BaseBoard Manufacturer:"Microsoft Corporation" BIOS Mode:"UEFI" BIOS Version/Date:"Microsoft Corporation 13.101.140 , 12/16/2021" CD or DVD:"Not Available" Embedded Controller Version:"255.255" Platform Role:"Mobile" Processor:"Intel(R) Core(TM) i5-1035G7 CPU @ 1.20GHz , GenuineIntel" Secure Boot State:"On" SMBIOS Version:"3.3" Sound Card:"Intel(R) Display Audio" Sound Card:"Realtek High Definition Audio(SST)" System Manufacturer:"Microsoft Corporation" System Model:"Surface Laptop 3" System SKU:"Surface_Laptop_3_1867:1868" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"Not Available" - "Intel(R) Iris(R) Plus Graphics" Adapter Compatibility:"Intel Corporation" Adapter DAC Type:"Internal" Adapter RAM:"1.00 GB" Availability:"Running or Full Power" Bits Per Pixel:"32" - "Caption":"Intel(R) Iris(R) Plus Graphics" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Iris+Plus+Graphics" CoInstallers:"oem127.inf,iICLD_w10_DS_N,Internal,Intel(R) Iris(R) Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmdn64.sys" Driver Date:"06/15/2021 01:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdkmdn64.sys" Driver Provider:"Intel Corporation" Driver Version:"27.20.100.9621" INF:"oem127.inf" INF Section:"iICLD_w10_DS_N" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd12umd64.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 0, device 2, function 0" Manufacturer:"Intel Corporation" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_8A52&SUBSYS_00351414&REV_07\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"59 Hz" Refresh Rate - Maximum:"59 Hz" Refresh Rate - Minimum:"59 Hz" Resolution:"2256 X 1504" Scan Mode:"Noninterlaced" Service Name:"igfxn" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) Iris(R) Graphics Family" - "Memory" Physical Memory (Available):"1.24 GB" Physical Memory (Installed):"8 GB" Physical Memory (Total):"7.60 GB" - "BANK 0" Capacity:"4 GB" Channel:"ChannelA-DIMM0" Configured Clock Speed:"3733 MHz" Configured Voltage:"600 millivolts" Data Width:"32 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K4U6E3S4AA-MGCL" Serial Number:"Not Available" Status:"Not Available" Type:"Synchronous" - "BANK 2" Capacity:"4 GB" Channel:"ChannelB-DIMM0" Configured Clock Speed:"3733 MHz" Configured Voltage:"600 millivolts" Data Width:"32 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K4U6E3S4AA-MGCL" Serial Number:"Not Available" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"13.101.140, MSFT - 2" Caption:"Motherboard" - "Chipset":"I/O LPC Controller (U Premium) - 3482 for Intel(R) 495 Series" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=I%2fO+LPC+Controller+(U+Premium)+++3482+for++495+Series" Date:"12/16/2021 12:00 AM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"Microsoft Corporation" Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"Surface Laptop 3" Serial Number:"A30363010046015A" 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" - "Bluetooth Device (Personal Area Network)" Availability:"Running or Full Power" Caption:"Bluetooth Device (Personal Area Network)" 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:"bthpan.sys" Driver Date:"06/21/2006 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\bthpan.sys" Driver Provider:"Microsoft" Driver Version:"10.0.22000.653" Index:"0004" INF:"bthpan.inf" INF Section:"BthPan.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:"05/12/2022 01:13 PM" Location:"Not Available" MAC Address:"C8:34:8E:42:75:B7" Manufacturer:"Microsoft" Media Type: Net Connection ID:"Bluetooth Network Connection" NetCfgInstanceId:"{0ED40269-DC1A-4F1C-9A08-8E7549BB8168}" Number of VLANs:"0" PNP Device ID:"BTH\MS_BTHPAN\6&DBEFFE6&0&2" 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:"Bluetooth Device (Personal Area Network)" Service Name:"BthPan" 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: - "Intel(R) Wi-Fi 6 AX201 160MHz" Access Point:"e8:48:b8:e8:d7:15" Authentication:"WPA2-Personal" Availability:"Running or Full Power" - "Caption":"Intel(R) Wi-Fi 6 AX201 160MHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Wi+Fi+6+AX201+160MHz" Channel:"44" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Profile" Default IP Gateway:"192.168.0.1" DHCP Enabled:"Yes" DHCP Lease Expires:"05/13/2022 06:00 PM" DHCP Lease Obtained:"05/13/2022 04:00 PM" DHCP Server:"192.168.0.43" Driver:"Netwtw10.sys" Driver Date:"03/15/2022 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\Netwtw10.sys" Driver Provider:"Intel" Driver Version:"22.130.0.5" Index:"0002" INF:"oem119.inf" INF Section:"Install_GEN_QSR_HrP_201_AX_2x2_WinT_non_6e" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.0.111;fe80::8514:5512:6a95:595d" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"05/12/2022 01:13 PM" Location:"PCI bus 0, device 20, function 3" MAC Address:"C8:34:8E:42:75:B3" Manufacturer:"Intel Corporation" Media Type: Net Connection ID:"WiFi" NetCfgInstanceId:"{B26BC2E2-758E-4430-AB51-DF5903238E1E}" Network Name:"VM1557505_EXT" Network Type:"Infrastructure" Number of VLANs:"0" PNP Device ID:"PCI\VEN_8086&DEV_34F0&SUBSYS_00748086&REV_30\3&11583659&0&A3" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Wi-Fi 6 AX201 160MHz" Profile:"VM1557505_EXT" Radio Type:"802.11ac" Receive Rate:"390 Mbps" Service Name:"Netwtw10" Signal Strength:"85%" State:"connected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate:"162 Mbps" 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)" BgScanGlobalBlocking:Global BG Scan blocking:"Never (0)" 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/ax Wireless Mode:"4. 802.11ax (3)" 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)" - "TAP-Windows Adapter V9" Availability:"Running or Full Power" Caption:"TAP-Windows Adapter V9" 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:"tap0901.sys" Driver Date:"09/27/2019 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\tap0901.sys" Driver Provider:"TAP-Windows Provider V9" Driver Version:"9.24.2.601" Index:"0001" INF:"oem76.inf" INF Section:"tap0901.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:"05/12/2022 01:13 PM" Location:"Not Available" MAC Address:"00:FF:4A:24:2A:F5" Manufacturer:"TAP-Windows Provider V9" Media Type: Net Connection ID:"Local Area Connection" NetCfgInstanceId:"{4A242AF5-11F2-410D-928B-4201C15F8D46}" 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:"TAP-Windows Adapter V9" Service Name:"tap0901" 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 Kingdom" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 11 Home" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"5.50 GB" Physical Memory (Available):"1.25 GB" Physical Memory (Installed):"8 GB" Physical Memory (Total):"7.60 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.22000 Build 22000" Virtual Memory (Available):"4.59 GB" Virtual Memory (Total):"13.10 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" 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 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB5007575:"Update [1/5/2022]" KB5011650:"Update [4/15/2022]" KB5012674:"Update [5/11/2022]" KB5013628:"Update [5/12/2022]" KB5013943:"Security Update [5/12/2022]" - "Processor" - "Intel(R) Core(TM) i5-1035G7 CPU @ 1.20GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 126 Stepping 5" - "Chipset Name":"Intel(R) Core(TM) i5-1035G7 CPU @ 1.20GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i5+1035G7+CPU+" CPU Speed:"1.20 GHz" Current Voltage:"7. 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.22000.653" 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:"4 x 192 KB" Level 2 Cache:"4 x 2048 KB" Level 3 Cache:"6 MB" Load:"28%" Manufacturer:"GenuineIntel" Model:"126" Name:"Intel(R) Core(TM) i5-1035G7 CPU @ 1.20GHz" Number of Cores:"4" Number of Cores Enabled:"4" Number of Logical Processors:"8" Part Number:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000706E5" Revision:"32261" Serial Number:"Not Available" Service Name:"intelppm" Status:"OK" Stepping:"5" Version:"Not Available" - "Storage" - "HFM256GDGTNG-87A0A" Capablities:"Random Access, Supports Writing" Caption:"HFM256GDGTNG-87A0A" Cylinder - Total:"31130" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.22000.1" Error Code:"Device is working properly" Firmware Revision:"80041C00" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"HFM256GDGTNG-87A0A" Name:"\\.\PHYSICALDRIVE0" Partitions:"3" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_HFM256GDGTNG-87A\5&35068D21&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:"0" Sectors - Per Track:"63" Sectors - Total:"500103450" Serial Number:"ACE4_2E00_9591_9CD1." Size:"238.47 GB" Size – Available:"69.80 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"7938150" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Local Disk" Serial Number:"9CC039AA" Size:"237.23 GB" Size – Available:"69.81 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C02F000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C02E000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 "000000000100320000000000D71000C011010000250200C02D000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C02C000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 "000000000100320000000000D71000C011010000250200C02B000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C02A000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C011010000250200C029000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C028000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C027000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C026000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C011010000250200C025000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C024000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C023000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C022000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C011010000250200C021000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C020000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C011010000250200C01F000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C01E000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C011010000250200C01D000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C01C000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C011010000250200C01B000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C01A000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C011010000250200C019000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C018000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C017000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C016000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C015000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C014000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C013000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C012000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C011000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C010000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C00F000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C00E000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C00D000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C00C000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C00B000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C00A000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 server could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule {d57d2750-f971-408e-8e55-cfddb37e60ae} failed with error 0x57 ------------------------------------------------------------------- Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule {d57d2750-f971-408e-8e55-cfddb37e60ae} failed with error 0x57 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{AFE43773-E1F8-4EBB-8536-576AB86AFE9A} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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:50:01 on ‎12/‎05/‎2022 was unexpected. ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B709} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B708} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B707} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B706} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B705} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B704} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B703} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B702} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B714} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B713} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B712} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B711} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B710} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B701} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B700} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register 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.22000.1_neutral_neutral_cw5n1h2txyewy!Windows.Networking.BackgroundTransfer.Internal.BackgroundTransferTask.ClassId.1 did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.22000.1_neutral_neutral_cw5n1h2txyewy!Windows.Networking.BackgroundTransfer.Internal.BackgroundTransferTask.ClassId.1 did not register with DCOM within the required timeout. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc000000e ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc000000e ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B700} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (78:2b:64:f0:72:96) failed. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (78:2b:64:f0:72:96) failed. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule {d57d2750-f971-408e-8e55-cfddb37e60ae} failed with error 0x57 ------------------------------------------------------------------- Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule {d57d2750-f971-408e-8e55-cfddb37e60ae} failed with error 0x57 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:802:f546:22bb:92c4:482:11 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:802:f546:22bb:92c4:482:a with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:802:f546:22bb:92c4:482:7 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:d456:2e37:7e0c:5b09 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:116:5401:e7a6:906c with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:7 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The PenService_1062278b service terminated with the following service-specific error: Unspecified error ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Write fails, Status = 0xc0000186 ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:22bb:92c4:482:9 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:1c02:9b5b:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NBLGGH4QGHW-Microsoft.MicrosoftStickyNotes. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NBLGGH4QGHW-Microsoft.MicrosoftStickyNotes. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Write fails, Status = 0xc0000186 ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Function Discovery Resource Publication service terminated with the following error: Operation aborted ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Function Discovery Resource Publication service terminated with the following error: Operation aborted ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} 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. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} 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. ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8aa:7be4:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8aa:7be4:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8aa:7be4:647a:1e23:ad94:a11a with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8aa:7be4:647a:1e23:ad94:a11a with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8aa:7be4:647a:1e23:ad94:a11a with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8aa:7be4:647a:1e23:ad94:a11a with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8aa:7be4:647a:1e23:ad94:a11a with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8aa:7be4:1d07:5a61:fce4:3e80 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8aa:7be4:3102:16ee:7994:a12d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:4ddc:1530:7e5a:729c with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:4b with the system having network hardware address F8-B9-5A-27-7A-26. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:4b with the system having network hardware address F8-B9-5A-27-7A-26. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:647a:1e23:ad94:a11a with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:d14:9763:b9bf:4633 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:1c1a:ca51:aa45:2219 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B700} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:4b with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server windows.immersivecontrolpanel_10.0.6.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:957a:d00:aeb5:f1cb with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:957a:d00:aeb5:f1cb with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:957a:d00:aeb5:f1cb with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:7569:acbc:812c:8fb3 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:4b with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:4b with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:4b with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:4b with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:4b with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:7569:acbc:812c:8fb3 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:7569:acbc:812c:8fb3 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:7569:acbc:812c:8fb3 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:1f6:420a:572f:abd6 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (74:f9:ca:4a:87:21) failed. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:3068:444c:917:398e with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:54 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:1c3d:8f35:142:29d7 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:1c3d:8f35:142:29d7 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:43 with the system having network hardware address 28-16-A8-4B-AD-D8. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:a177:a7b8:48ab:d7ab with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:43 with the system having network hardware address 28-16-A8-4B-AD-D8. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9PGGJ4LF6SPV-Microsoft.Windows.Photos.DLC.Main. ------------------------------------------------------------------- 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 system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:43 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9PGGJ4LF6SPV-Microsoft.Windows.Photos.DLC.Main. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:43 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9PGGJ4LF6SPV-Microsoft.Windows.Photos.DLC.Main. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:43 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9PGGJ4LF6SPV-Microsoft.Windows.Photos.DLC.Main. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:43 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:74a2:d83b:2400:579a with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:43 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:49 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:47 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:b9ee:a14a:7bc2:4338 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:55a4:4876:b988:5ca1 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address F8-B9-5A-27-7A-26. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address F8-B9-5A-27-7A-26. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Network Setup 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 Network Setup Service service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:804:34ac:22bb:92c4:482:23 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x800706BE: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NFFX4SZZ23L-Microsoft.549981C3F5F10. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NFFX4SZZ23L-Microsoft.549981C3F5F10. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NFFX4SZZ23L-Microsoft.549981C3F5F10. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NFFX4SZZ23L-Microsoft.549981C3F5F10. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NFFX4SZZ23L-Microsoft.549981C3F5F10. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NFFX4SZZ23L-Microsoft.549981C3F5F10. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NFFX4SZZ23L-Microsoft.549981C3F5F10. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NFFX4SZZ23L-Microsoft.549981C3F5F10. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Write fails, Status = 0xc0000186 ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NBLGGH4QGHW-Microsoft.MicrosoftStickyNotes. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- 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 {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (2c:41:a1:ba:8a:06) failed. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The Windows Update 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 Windows Update service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The Microsoft Defender Antivirus Service service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Write fails, Status = 0xc0000186 ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} 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. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {B55DB943-A00A-4E34-A546-0AF0EB20D2CD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ3P2-MICROSOFT.ZUNEVIDEO. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service WaaSMedicSvc with arguments "Unavailable" in order to run the server: {72566E27-1ABB-4EB3-B4F0-EB431CB1CB32} ------------------------------------------------------------------- The Windows Update Medic 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 Windows Update Medic Service service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} 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. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Network Connected Devices Auto-Setup 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 Network Connected Devices Auto-Setup service to connect. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc00000b5 ------------------------------------------------------------------- Surface Tcon Driver TP Write fails, Status = 0xc00000b5 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8} ------------------------------------------------------------------- The Windows Search 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 Windows Search service to connect. ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B700} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9489FEB2-1925-4D01-B788-6D912C70F7F2} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Write fails, Status = 0xc0000001 ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc000000e ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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 could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Write fails, Status = 0xc0000186 ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Windows Update 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 Windows Update service to connect. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc000000e ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Surface Tcon Driver TP Write fails, Status = 0xc0000186 ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Software Protection service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Software Protection service to connect. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:822:c2e:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:822:c2e:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:822:c2e:55a4:4876:b988:5ca1 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:822:c2e:22bb:92c4:482:6 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:f096:f607:1c6d:9510 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:95e8:ad3b:6c75:bf08 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WinHTTP Web Proxy Auto-Discovery Service service to connect. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:22bb:92c4:482:13 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:22bb:92c4:482:13 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:22bb:92c4:482:13 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Surface Tcon Driver TP Read fails, Status = 0xc0000186 ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:216a:5476:8c32:336 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:7cfb:2589:2c39:ea58 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:adb3:fb67:8ce6:dfa7 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:b011:502b:944d:6c6a with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:d14:9763:b9bf:4633 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:22bb:92c4:482:14 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:22bb:92c4:482:10 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:22bb:92c4:482:9 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:22bb:92c4:482:4 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a7:69b7:d14:9763:b9bf:4633 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:95b5:9c88:e0d6:6759 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:5407:5202:84c7:abe0 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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 {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The AppX Deployment Service (AppXSVC) 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 AppX Deployment Service (AppXSVC) service to connect. ------------------------------------------------------------------- The Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. ------------------------------------------------------------------- The server Windows.Internal.Management.Enrollment.Enroller did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Device Management Enrollment Service service terminated with the following error: Unspecified error ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ3PR-MICROSOFT.WINDOWSALARMS. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address fd22:bb92:c404:8200:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-10 Update for Windows SV Version 21H2 for x64-based Systems (KB4023057). ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:55a4:4876:b988:5ca1 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:55a4:4876:b988:5ca1 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:55a4:4876:b988:5ca1 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:b with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address EA-48-B8-4B-AD-D8. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:a974:4071:bd73:c942 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:9c54:a25f:d286:a1a3 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:55e6:d10f:9241:8049 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} 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_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:8514:5512:6a95:595d with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {1c0ea150-a849-4987-b4af-16421af1c912}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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 system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B26BC2E2-758E-4430-AB51-DF5903238E1E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 2a01:4c8:8a1:a106:22bb:92c4:482:2 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Printer Extensions and Notifications service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. ------------------------------------------------------------------- The Network List Service service terminated with the following error: The device is not ready. ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 5/13/2022, 16:07:03 Machine name: ARGYROPC Machine Id: {99816984-EB53-4F7A-A312-ED064EFC929D} Operating System: Windows 11 Home 64-bit (10.0, Build 22000) (22000.co_release.210604-1628) Language: English (Regional Setting: English) System Manufacturer: Microsoft Corporation System Model: Surface Laptop 3 BIOS: 13.101.140 (type: UEFI) Processor: Intel(R) Core(TM) i5-1035G7 CPU @ 1.20GHz (8 CPUs), ~1.5GHz Memory: 8192MB RAM Available OS Memory: 7778MB RAM Page File: 8725MB used, 4684MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 144 DPI (150 percent) System DPI Setting: 144 DPI (150 percent) DWM DPI Scaling: UnKnown Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.2.2 DxDiag Version: 10.00.22000.0653 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Display Tab 2: No problems found. Sound Tab 1: 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: Intel(R) Iris(R) Plus Graphics Manufacturer: Intel Corporation Chip type: Intel(R) Iris(R) Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_8A52&SUBSYS_00351414&REV_07 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: 4017 MB Dedicated Memory: 128 MB Shared Memory: 3889 MB Current Mode: 2256 x 1504 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.648438,0.330078), Green(0.320312,0.597656), Blue(0.155273,0.065430), White Point(0.345703,0.358398) Display Luminance: Min Luminance = 0.500000, Max Luminance = 400.000000, MaxFullFrameLuminance = 400.000000 Monitor Name: Surface Panel Monitor Model: LQ135P1JX51 Monitor Id: SHP14B3 Native Mode: 2256 x 1504(p) (59.999Hz) Output Type: Internal Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd12umd64.dll Driver File Version: 27.20.0100.9621 (English) Driver Version: 27.20.100.9621 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: DriverSupportState:AlwaysOff Enabled:False Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: DISABLE_HWSCH Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 15/06/2021 01:00:00, 1481064 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-C912-11CF-3152-5120BCC2D635} Vendor ID: 0x8086 Device ID: 0x8A52 SubSys ID: 0x00351414 Revision ID: 0x0007 Driver Strong Name: oem127.inf:5f63e53448217367:iICLD_w10_DS_N:27.20.100.9621:PCI\VEN_8086&DEV_8A52&SUBSYS_00351414 Rank Of Driver: 00CF0001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} DXVA2_ModeVP8_VLD {442B942A-B4D9-4940-BC45-A882E5F919F3} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {9B31316B-F204-455D-8A8C-9345DCA77C01} {AFE4285C-AB63-4B2D-8278-E6BAACEA2CE9} {277DE9C5-ED83-48DD-AB8F-AC2D24B22943} {04C5BA10-4E9A-4B8E-8DBF-4F4B48AFA27C} {0ACEF8BC-285F-415D-AB22-7BF2527A3D2E} {24D19FCA-C5A2-4B8E-9F93-F8F6EF15C890} {353ACA91-D945-4C13-AE7E-469060FAC8D8} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {B8B28E0C-ECAB-4217-8C82-EAAA9755AAF0} {8732ECFD-9747-4897-B42A-E534F9FF2B7A} {E139B5CA-47B2-40E1-AF1C-AD71A67A1836} {056A6E36-F3A8-4D00-9663-7E9430358BF9} {5415A68C-231E-46F4-878B-5E9A22E967E9} {161BE912-44C2-49C0-B61E-D946852B32A1} {580DA148-E4BF-49B1-943B-4214AB05A6FF} {CEE393AB-1030-4F7B-8DBC-55629C72F17E} {87B2AE39-C9A5-4C53-86B8-A52D7EDBA488} {10E19AC8-BF39-4443-BEC3-1B0CBFE4C7AA} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {E484DCB8-CAC9-4859-99F5-5C0D45069089} {41A5AF96-E415-4B0C-9D03-907858E23E78} {6A6A81BA-912A-485D-B57F-CCD2D37B8D94} {E4E3CF5B-97D2-4658-AACB-366E3EE2CEEE} {FD9D9559-0FD3-4917-A9A7-07E714EE9EF9} {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {68A21C7B-D58F-4E74-9993-E4B8172B19A0} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {1D5C4D76-B55A-4430-904C-3383A7AE3B16} {50925B7B-E931-4978-A12A-586630F095F9} {B69C20E0-2508-8790-0305-875499E0A2D0} {49761BEC-4B63-4349-A5FF-87FFDF088466} Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 3 MPO Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) MPO Stretch: 21.000X - 0.334X MPO Media Hints: rotation, colorspace Conversion MPO Formats: NV12,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM PanelFitter Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) PanelFitter Stretch: 21.000X - 0.334X Extension Drivers: Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext_av.inf_amd64_9a86355e8be248ae\iigd_ext_av.inf Driver Version: 25.20.100.7101 Driver Date: 08/07/2019 Driver Provider: Intel Corporation Catalog Attributes: Universal:N/A Declarative:True Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext_av.inf_amd64_ead15890807923bd\iigd_ext_av.inf Driver Version: 27.20.100.9621 Driver Date: 06/16/2021 Driver Provider: Intel Corporation Catalog Attributes: Universal:N/A Declarative:True Component Drivers: Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A Card name: Intel(R) Iris(R) Plus Graphics Manufacturer: Intel Corporation Chip type: Intel(R) Iris(R) Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_8A52&SUBSYS_00351414&REV_07 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: 4017 MB Dedicated Memory: 128 MB Shared Memory: 3889 MB Current Mode: 2560 x 1440 (32 bit) (75Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.639648,0.330078), Green(0.299805,0.599609), Blue(0.149414,0.059570), 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: Q24V4W1G5 Monitor Id: AOC2404 Native Mode: 2560 x 1440(p) (59.951Hz) 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\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd12umd64.dll Driver File Version: 27.20.0100.9621 (English) Driver Version: 27.20.100.9621 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: DriverSupportState:AlwaysOff Enabled:False Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: DISABLE_HWSCH Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 15/06/2021 01:00:00, 1481064 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-C912-11CF-3152-5120BCC2D635} Vendor ID: 0x8086 Device ID: 0x8A52 SubSys ID: 0x00351414 Revision ID: 0x0007 Driver Strong Name: oem127.inf:5f63e53448217367:iICLD_w10_DS_N:27.20.100.9621:PCI\VEN_8086&DEV_8A52&SUBSYS_00351414 Rank Of Driver: 00CF0001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} DXVA2_ModeVP8_VLD {442B942A-B4D9-4940-BC45-A882E5F919F3} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {9B31316B-F204-455D-8A8C-9345DCA77C01} {AFE4285C-AB63-4B2D-8278-E6BAACEA2CE9} {277DE9C5-ED83-48DD-AB8F-AC2D24B22943} {04C5BA10-4E9A-4B8E-8DBF-4F4B48AFA27C} {0ACEF8BC-285F-415D-AB22-7BF2527A3D2E} {24D19FCA-C5A2-4B8E-9F93-F8F6EF15C890} {353ACA91-D945-4C13-AE7E-469060FAC8D8} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {B8B28E0C-ECAB-4217-8C82-EAAA9755AAF0} {8732ECFD-9747-4897-B42A-E534F9FF2B7A} {E139B5CA-47B2-40E1-AF1C-AD71A67A1836} {056A6E36-F3A8-4D00-9663-7E9430358BF9} {5415A68C-231E-46F4-878B-5E9A22E967E9} {161BE912-44C2-49C0-B61E-D946852B32A1} {580DA148-E4BF-49B1-943B-4214AB05A6FF} {CEE393AB-1030-4F7B-8DBC-55629C72F17E} {87B2AE39-C9A5-4C53-86B8-A52D7EDBA488} {10E19AC8-BF39-4443-BEC3-1B0CBFE4C7AA} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {E484DCB8-CAC9-4859-99F5-5C0D45069089} {41A5AF96-E415-4B0C-9D03-907858E23E78} {6A6A81BA-912A-485D-B57F-CCD2D37B8D94} {E4E3CF5B-97D2-4658-AACB-366E3EE2CEEE} {FD9D9559-0FD3-4917-A9A7-07E714EE9EF9} {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {68A21C7B-D58F-4E74-9993-E4B8172B19A0} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {1D5C4D76-B55A-4430-904C-3383A7AE3B16} {50925B7B-E931-4978-A12A-586630F095F9} {B69C20E0-2508-8790-0305-875499E0A2D0} {49761BEC-4B63-4349-A5FF-87FFDF088466} Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 3 MPO Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) MPO Stretch: 21.000X - 0.334X MPO Media Hints: rotation, colorspace Conversion MPO Formats: NV12,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM PanelFitter Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) PanelFitter Stretch: 21.000X - 0.334X Extension Drivers: Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext_av.inf_amd64_9a86355e8be248ae\iigd_ext_av.inf Driver Version: 25.20.100.7101 Driver Date: 08/07/2019 Driver Provider: Intel Corporation Catalog Attributes: Universal:N/A Declarative:True Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext_av.inf_amd64_ead15890807923bd\iigd_ext_av.inf Driver Version: 27.20.100.9621 Driver Date: 06/16/2021 Driver Provider: Intel Corporation Catalog Attributes: Universal:N/A Declarative:True ------------- Sound Devices ------------- Description: Speakers (Realtek High Definition Audio(SST)) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0274&SUBSYS_10EC11B2&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: RTKVHD64.sys Driver Version: 6.0.8936.1 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 13/04/2020 01:00:00, 7327824 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 Array (Realtek High Definition Audio(SST)) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: RTKVHD64.sys Driver Version: 6.0.8936.1 (English) Driver Attributes: Final Retail Date and Size: 13/04/2020 01:00:00, 7327824 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 3 --------------------- FriendlyName: Surface Camera Front Category: Camera SymbolicLink: \\?\usb#vid_045e&pid_0990&mi_00#6&db32c28&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 SensorOrientation: 0 Manufacturer: Microsoft HardwareID: USB\VID_045E&PID_0990&REV_1037&MI_00,USB\VID_045E&PID_0990&MI_00 DriverDesc: USB Video Device DriverProvider: Microsoft DriverVersion: 10.0.22000.653 DriverDateEnglish: 6/21/2006 00:00:00 DriverDateLocalized: 21/06/2006 00:00:00 Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: Surface Camera Front Parent: USB\VID_045E&PID_0990\200901010001 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {D73D0ED7-7D0E-40D6-9E62-3235075A287B} MFT0: n/a DMFT: n/a CustomCaptureSource: n/a DependentStillCapture: n/a EnablePlatformDMFT: True DMFTChain: n/a EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a MSXUCapability: 0x0000000e ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 FriendlyName: AvStream Media Device Category: Sensor SymbolicLink: \\?\usb#vid_045e&pid_0990&mi_02#6&db32c28&0&0002#{24e552d7-6523-47f7-a647-d3465bf1f5ca}\global Location: Front Rotation: 0 SensorOrientation: 0 Manufacturer: Microsoft HardwareID: USB\VID_045E&PID_0990&REV_1037&MI_02,USB\VID_045E&PID_0990&MI_02 DriverDesc: USB Video Device DriverProvider: Microsoft DriverVersion: 10.0.22000.653 DriverDateEnglish: 6/21/2006 00:00:00 DriverDateLocalized: 21/06/2006 00:00:00 Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: Surface IR Camera Front Parent: USB\VID_045E&PID_0990\200901010001 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {D73D0ED7-7D0E-40D6-9E62-3235075A287B} MFT0: n/a DMFT: n/a CustomCaptureSource: n/a DependentStillCapture: n/a EnablePlatformDMFT: n/a DMFTChain: n/a EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a MSXUCapability: 0x00000120 ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 FriendlyName: AvStream Media Device Category: Sensor Group SymbolicLink: \\?\swd#sgdevapi#d13ea2ad66ff6670bcf5f7229173a0a55d22a821e871a2d31ec890dff9dc124e#{669c7214-0a88-4311-a7f3-4e79820e33bd}\d13ea2ad66ff6670bcf5f7229173a0a55d22a821e871a2d31ec890dff9dc124e DeviceSymbolicLinks: \\?\USB#VID_045E&PID_0990&MI_00#6&db32c28&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global,\\?\USB#VID_045E&PID_0990&MI_02#6&db32c28&0&0002#{24e552d7-6523-47f7-a647-d3465bf1f5ca}\global ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},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: HID-compliant vendor-defined device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0932 FF Driver: n/a Device Name: Precise Touch Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0983 FF Driver: n/a Device Name: Surface Hid Mini Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x09AE FF Driver: n/a Device Name: Surface Hid Mini Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x09AF FF Driver: n/a Device Name: Precise Touch Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0983 FF Driver: n/a Device Name: Surface Hid Mini Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x09AE FF Driver: n/a Device Name: Precise Touch Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0983 FF Driver: n/a Device Name: HID-compliant vendor-defined device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0932 FF Driver: n/a Device Name: Precise Touch Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0983 FF Driver: n/a Device Name: Precise Touch Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0983 FF Driver: n/a Device Name: Surface Hid Mini Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x09AF FF Driver: n/a Device Name: Converted Portable Device Control device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0000 FF Driver: n/a Device Name: Surface Arc Mouse Integration Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0932 FF Driver: n/a Device Name: Surface Hid Mini Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x09AF FF Driver: n/a Device Name: Converted Portable Device Control device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0000 FF Driver: n/a Device Name: Surface Tcon Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0555 FF Driver: n/a Device Name: Surface Hid Mini Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0922 FF Driver: n/a Device Name: HID-compliant consumer control device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0932 FF Driver: n/a Device Name: Surface Hid Mini Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0922 FF Driver: n/a Device Name: Virtual HID Framework (VHF) HID device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0xF002 FF Driver: n/a Device Name: Surface Hid Mini Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0922 FF Driver: n/a Device Name: HID-compliant vendor-defined device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0932 FF Driver: n/a Device Name: Virtual HID Framework (VHF) HID device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0xF002 FF Driver: n/a Device Name: Virtual HID Framework (VHF) HID device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0xF001 FF Driver: n/a Device Name: Control Interface Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x094F FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x34ED | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 1/5/2022 18:45:31, 696656 bytes | +-+ Intel(R) Wireless Bluetooth(R) | | Vendor/Product ID: 0x8087, 0x0026 | | Location: Port_#0010.Hub_#0001 | | Matching Device ID: USB\VID_8087&PID_0026&REV_0002 | | Lower Filters: ibtusb | | Service: BTHUSB | | Driver: ibtusb.sys, 3/8/2022 18:55:18, 7180392 bytes | | Driver: BTHUSB.SYS, 5/11/2022 21:57:23, 118784 bytes | | Driver: bthport.sys, 5/11/2022 21:57:23, 1916928 bytes | | | +-+ Microsoft Bluetooth LE Enumerator | | | Matching Device ID: BTH\MS_BTHLE | | | Service: BthLEEnum | | | Driver: Microsoft.Bluetooth.Legacy.LEEnumerator.sys, 5/11/2022 21:57:23, 135168 bytes | | | | | +-+ Bluetooth LE Device | | | | Location: Bluetooth LE Device | | | | Matching Device ID: BTHLE\GenericDevice | | | | Service: BthLEEnum | | | | Driver: Microsoft.Bluetooth.Legacy.LEEnumerator.sys, 5/11/2022 21:57:23, 135168 bytes | | | | | | | +-+ Bluetooth Low Energy GATT compliant HID device | | | | | Vendor/Product ID: 0x0020, 0x0093 | | | | | Location: Bluetooth LE Device | | | | | Matching Device ID: BTHLEDevice\{00001812-0000-1000-8000-00805f9b34fb} | | | | | Lower Filters: WUDFRd | | | | | Service: mshidumdf | | | | | Driver: Microsoft.Bluetooth.Profiles.HidOverGatt.dll, 5/11/2022 21:57:23, 221184 bytes | | | | | | | | | +-+ HID-compliant mouse | | | | | | Vendor/Product ID: 0x0020, 0x0093 | | | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | | | Service: mouhid | | | | | | Driver: mouhid.sys, 5/11/2022 21:57:23, 65536 bytes | | | | | | Driver: mouclass.sys, 5/11/2022 21:57:23, 91488 bytes | | | | | | | | | | +-+ HID Keyboard Device | | | | | | Vendor/Product ID: 0x0020, 0x0093 | | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | | Service: kbdhid | | | | | | Driver: kbdhid.sys, 5/11/2022 21:57:23, 69632 bytes | | | | | | Driver: kbdclass.sys, 5/11/2022 21:57:23, 91488 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + HID Keyboard Device | Vendor/Product ID: 0x045E, 0xF001 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 5/11/2022 21:57:23, 69632 bytes | Driver: kbdclass.sys, 5/11/2022 21:57:23, 91488 bytes | + HID Keyboard Device | Vendor/Product ID: 0x045E, 0x09AE | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 5/11/2022 21:57:23, 69632 bytes | Driver: kbdclass.sys, 5/11/2022 21:57:23, 91488 bytes | + HID Keyboard Device | Vendor/Product ID: 0x045E, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 5/11/2022 21:57:23, 69632 bytes | Driver: kbdclass.sys, 5/11/2022 21:57:23, 91488 bytes | + HID-compliant mouse | Vendor/Product ID: 0x045E, 0x09AF | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 5/11/2022 21:57:23, 65536 bytes | Driver: mouclass.sys, 5/11/2022 21:57:23, 91488 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 71.5 GB Total Space: 242.9 GB File System: NTFS Model: HFM256GDGTNG-87A0A -------------- System Devices -------------- Name: Intel(R) Serial IO I2C Host Controller - 34C5 Device ID: PCI\VEN_8086&DEV_34C5&SUBSYS_72708086&REV_30\3&11583659&0&C8 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_icl.inf_amd64_04e193b8806eca82\iaLPSS2_I2C.sys, 30.100.1916.0001 (English), 5/8/2019 01:59:22, 197008 bytes Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_34C8&SUBSYS_72708086&REV_30\3&11583659&0&FB Driver: C:\WINDOWS\System32\DriverStore\FileRepository\intcaudiobus.inf_amd64_9d9e7ac5673212b5\IntcAudioBus.sys, 10.24.0000.3694 (English), 3/23/2020 08:32:46, 289232 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.22000.0653 (English), 5/11/2022 21:57:20, 135168 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.22000.0653 (English), 5/11/2022 21:57:20, 462848 bytes Name: PCI standard RAM Controller Device ID: PCI\VEN_8086&DEV_34EF&SUBSYS_00000000&REV_30\3&11583659&0&A2 Driver: n/a Name: Standard NVM Express Controller Device ID: PCI\VEN_1C5C&DEV_1327&SUBSYS_00001C5C&REV_00\919C9195002EE4AC00 Driver: C:\WINDOWS\system32\DRIVERS\stornvme.sys, 10.00.22000.0527 (English), 3/11/2022 11:31:08, 226672 bytes Name: Intel(R) Serial IO I2C Host Controller - 34E8 Device ID: PCI\VEN_8086&DEV_34E8&SUBSYS_72708086&REV_30\3&11583659&0&A8 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_icl.inf_amd64_04e193b8806eca82\iaLPSS2_I2C.sys, 30.100.1916.0001 (English), 5/8/2019 01:59:22, 197008 bytes Name: Intel(R) Dynamic Tuning Processor Participant Device ID: PCI\VEN_8086&DEV_8A03&SUBSYS_72708086&REV_03\3&11583659&0&20 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\esif_lf.sys, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 408456 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\dptf_cpu.sys, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 74120 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\esif_uf.exe, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 2141064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\esif_umdf2.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 911744 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\Dptf.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 2177928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyRfim.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 726408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyActive.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 726920 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyActive2.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 911240 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyAdaptivePerformance.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 1065864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyCritical.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 680328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyConfigTdp.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 695680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyPassive.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 1021832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyPassive2.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 962952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyPid.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 892296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyPowerBoss.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 1245568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyVirtualSensor.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 865160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\DptfPolicyPowerShare.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 871816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\upe_wwan.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 126848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\upe_wifi.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 63360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\upe_nvme.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 106376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\upe_battery.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 66952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\upe_socwc.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 215432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\dptf_helper.exe, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 517512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\esif_cmp.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 136584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\esif_ws.dll, 8.06.10401.9906 (English), 6/22/2019 01:36:14, 229280 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_4a3ae74cfa6c37d6\dsp.dv, 6/22/2019 01:36:14, 685723 bytes Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_34E0&SUBSYS_72708086&REV_30\3&11583659&0&B0 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\heci.inf_amd64_e54ec85669ef8010\x64\TeeDriverW10x64.sys, 2120.100.0000.1085 (English), 7/21/2021 06:34:38, 326576 bytes Name: Intel(R) Iris(R) Plus Graphics Device ID: PCI\VEN_8086&DEV_8A52&SUBSYS_00351414&REV_07\3&11583659&0&10 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdkmdn64.sys, 27.20.0100.9621 (English), 7/8/2021 10:17:26, 28628032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iglhxsn64.vp, 7/8/2021 09:48:56, 5719 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd10iumd64.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:36, 18920456 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd11dxva64.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:42, 71409976 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd12dxva64.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:50, 71313384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd12umd64.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:56, 11835704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdgmm64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:16, 3435528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igfxcmrt64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:34, 224592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igfx11cmrt64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:30, 227768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdumdim64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:26, 1481064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdail64.dll, 7/8/2021 10:17:22, 202616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd9dxva64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:04, 71053128 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iga64.dll, 7/8/2021 10:17:22, 2963984 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igc64.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:30, 48673832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\SPIRVDLL.dll, 7/8/2021 10:18:38, 4166488 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\UniversalAdapter64.dll, 7/8/2021 10:19:34, 338000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\opencl-clang64.dll, 2.00.0009.0000 (English), 7/8/2021 10:19:30, 83404184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdfcl64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:12, 1060792 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdmd64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:22, 7857680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdml64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:24, 4335192 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdde64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:08, 430200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdinfo64.dll, 7/8/2021 10:18:18, 165824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdext64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:10, 292088 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd10iumd32.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:34, 14795112 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd11dxva32.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:40, 69797560 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd12dxva32.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:46, 69698928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd12umd32.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:54, 11496608 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdgmm32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:12, 2560384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdumdim32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:26, 1313424 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdail32.dll, 7/8/2021 10:17:22, 166776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igd9dxva32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:00, 69456128 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igfxcmrt32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:30, 181032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igfx11cmrt32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:28, 183072 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iga32.dll, 7/8/2021 10:17:22, 2379920 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igc32.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:26, 41689240 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\SPIRVDLL32.dll, 7/8/2021 10:18:40, 3194216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\UniversalAdapter32.dll, 7/8/2021 10:19:32, 282216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\opencl-clang32.dll, 2.00.0009.0000 (English), 7/8/2021 10:19:26, 61888840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdfcl32.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:24, 961400 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdmd32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:20, 6600432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdml32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:22, 3361192 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdde32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:06, 350216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdinfo32.dll, 7/8/2021 10:18:16, 139760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdext32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:10, 235064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iglhxo64.vp, 7/8/2021 09:48:56, 42513 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iglhxc64.vp, 7/8/2021 09:48:56, 44194 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iglhxg64.vp, 7/8/2021 09:48:56, 43760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iglhxo64_dev.vp, 7/8/2021 09:48:56, 43143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iglhxc64_dev.vp, 7/8/2021 09:48:56, 43214 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iglhxg64_dev.vp, 7/8/2021 09:48:56, 43732 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iglhxa64.vp, 7/8/2021 09:48:56, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\iglhxa64.cpa, 7/8/2021 09:48:56, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\IntelCpHDCPSvc.exe, 27.20.0100.9621 (English), 7/8/2021 10:18:06, 365136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\cp_resources.bin, 7/8/2021 09:48:52, 2415596 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\ig11icd64.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:10, 16841080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\ig11icd32.dll, 27.20.0100.9621 (English), 7/8/2021 10:17:10, 13483896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\OSSCOPYRIGHT.txt, 7/8/2021 09:49:02, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igvk64.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:42, 18552656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igvk64.json, 7/8/2021 09:48:56, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\VulkanRT-EULA.txt, 7/8/2021 09:49:02, 4008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igvk32.dll, 27.20.0100.9621 (English), 7/8/2021 10:18:38, 16707920 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igvk32.json, 7/8/2021 09:48:56, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\vulkan-1-64.dll, 1.02.0162.0001 (English), 7/8/2021 10:18:46, 1102368 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\vulkaninfo-64.exe, 1.02.0162.0001 (English), 7/8/2021 10:18:50, 1859664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\vulkan-1-32.dll, 1.02.0162.0001 (English), 7/8/2021 10:18:42, 956448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\vulkaninfo-32.exe, 1.02.0162.0001 (English), 7/8/2021 10:18:46, 1440328 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.03.0204.0001 (English), 5/6/2022 13:19:14, 1145600 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.03.0204.0001 (English), 5/6/2022 13:19:20, 1526416 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.03.0204.0001 (English), 5/6/2022 13:19:14, 1145600 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.03.0204.0001 (English), 5/6/2022 13:19:20, 1526416 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.03.0204.0001 (English), 5/6/2022 13:19:16, 1432304 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.03.0204.0001 (English), 5/6/2022 13:19:20, 1969824 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.03.0204.0001 (English), 5/6/2022 13:19:16, 1432304 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.03.0204.0001 (English), 5/6/2022 13:19:20, 1969824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 7/8/2021 10:18:14, 370520 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdrcl32.dll, 23.20.0100.9621 (English), 7/8/2021 10:17:32, 4129136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 7/8/2021 10:18:16, 507736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\ze_loader.dll, 1.02.0003.0000 (English), 7/8/2021 10:18:52, 429928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\ze_validation_layer.dll, 1.02.0003.0000 (English), 7/8/2021 10:18:54, 145776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\ze_tracing_layer.dll, 1.02.0003.0000 (English), 7/8/2021 10:18:52, 614256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\ControlLib.dll, 1.00.0011.0000 (English), 7/8/2021 10:17:00, 354664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\igdrcl64.dll, 23.20.0100.9621 (English), 7/8/2021 10:17:32, 4685168 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\ze_intel_gpu64.dll, 7/8/2021 10:18:50, 4279144 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 3.00.0001.0000 (English), 5/11/2022 22:00:44, 78336 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 3.00.0001.0000 (English), 5/11/2022 22:00:43, 114688 bytes Driver: C:\WINDOWS\system32\ze_loader.dll, 1.02.0003.0000 (English), 7/8/2021 10:18:52, 429928 bytes Driver: C:\WINDOWS\system32\ze_validation_layer.dll, 1.02.0003.0000 (English), 7/8/2021 10:18:54, 145776 bytes Driver: C:\WINDOWS\system32\ze_tracing_layer.dll, 1.02.0003.0000 (English), 7/8/2021 10:18:52, 614256 bytes Driver: C:\WINDOWS\system32\ControlLib.dll, 1.00.0011.0000 (English), 7/8/2021 10:17:00, 354664 bytes Driver: C:\WINDOWS\SysWow64\libmfxhw32.dll, 11.21.0004.0014 (English), 7/8/2021 10:18:58, 257096 bytes Driver: C:\WINDOWS\SysWow64\mfxplugin32_hw.dll, 1.21.0004.0014 (English), 7/8/2021 10:18:18, 13499224 bytes Driver: C:\WINDOWS\system32\libmfxhw64.dll, 22.03.0028.0415 (English), 5/6/2022 13:20:40, 948552 bytes Driver: C:\WINDOWS\system32\mfxplugin64_hw.dll, 1.21.0004.0014 (English), 7/8/2021 10:18:20, 26671968 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 11.21.0004.0014 (English), 7/8/2021 10:18:42, 173136 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 11.21.0004.0014 (English), 7/8/2021 10:18:46, 148424 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfxplugin64_hw.dll, 1.21.0004.0014 (English), 7/8/2021 10:18:20, 26671968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfxplugin64_av1e_gacc.dll, 7/8/2021 10:18:56, 5570880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\intel_gfx_api-x64.dll, 11.21.0004.0014 (English), 7/8/2021 10:18:42, 173136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfxplugin32_hw.dll, 1.21.0004.0014 (English), 7/8/2021 10:18:18, 13499224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfxplugin32_av1e_gacc.dll, 7/8/2021 10:18:56, 4576472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\intel_gfx_api-x86.dll, 11.21.0004.0014 (English), 7/8/2021 10:18:46, 148424 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_h264ve_32.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:12, 2635040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_mjpgvd_32.dll, 11.21.0004.0014 (English), 7/8/2021 10:18:22, 2468208 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_h265ve_32.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:18, 2648152 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_vp9ve_32.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:20, 2643448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_encrypt_32.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:06, 2473120 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_av1hve_32.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:04, 2644984 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\c_32.cpa, 7/8/2021 09:48:52, 1361159 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\cpa_32.vp, 7/8/2021 09:48:52, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\dev_32.vp, 7/8/2021 09:48:52, 57143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\he_32.vp, 7/8/2021 09:48:52, 71877 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mj_32.vp, 7/8/2021 09:49:00, 67145 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\h265e_32.vp, 7/8/2021 09:48:52, 73525 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\vp9e_32.vp, 7/8/2021 09:49:02, 73036 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_av1hve_32.vp, 7/8/2021 09:49:00, 73093 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_h264ve_64.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:14, 3252416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_mjpgvd_64.dll, 11.21.0004.0014 (English), 7/8/2021 10:18:24, 3051888 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_h265ve_64.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:18, 3273016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_vp9ve_64.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:22, 3266872 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_encrypt_64.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:08, 3044976 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_av1hve_64.dll, 11.21.0004.0014 (English), 7/8/2021 10:19:06, 3268936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\c_64.cpa, 7/8/2021 09:48:52, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\cpa_64.vp, 7/8/2021 09:48:52, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\dev_64.vp, 7/8/2021 09:48:52, 56359 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\he_64.vp, 7/8/2021 09:48:52, 13665 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mj_64.vp, 7/8/2021 09:49:00, 13409 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\h265e_64.vp, 7/8/2021 09:48:52, 14257 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\vp9e_64.vp, 7/8/2021 09:49:02, 14116 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\mfx_mft_av1hve_64.vp, 7/8/2021 09:49:00, 14081 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\libmfxhw64.dll, 11.21.0004.0014 (English), 7/8/2021 10:18:54, 25637848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d73f88d32ddb95d3\libmfxhw32.dll, 11.21.0004.0014 (English), 7/8/2021 10:18:52, 24113944 bytes Name: I/O LPC Controller (U Premium) - 3482 for Intel(R) 495 Series Chipset Family On-Package Platform Controller Hub Device ID: PCI\VEN_8086&DEV_3482&SUBSYS_72708086&REV_30\3&11583659&0&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.22000.0001 (English), 6/5/2021 13:04:45, 53576 bytes Name: Intel(R) SPI (flash) Controller - 34A4 Device ID: PCI\VEN_8086&DEV_34A4&SUBSYS_72708086&REV_30\3&11583659&0&FD Driver: n/a Name: PCI standard host CPU bridge Device ID: PCI\VEN_8086&DEV_8A12&SUBSYS_72708086&REV_03\3&11583659&0&00 Driver: n/a Name: Intel(R) USB 3.10 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_8A13&SUBSYS_00000000&REV_03\3&11583659&0&68 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.22000.0469 (English), 2/11/2022 12:19:38, 656744 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.22000.0469 (English), 2/11/2022 12:19:38, 161512 bytes Name: Intel(R) PCI Express Root Port #9 - 34B0 Device ID: PCI\VEN_8086&DEV_34B0&SUBSYS_72708086&REV_30\3&11583659&0&E8 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22000.0653 (English), 5/11/2022 21:57:22, 537952 bytes Name: Intel(R) Serial IO I2C Host Controller - 34E9 Device ID: PCI\VEN_8086&DEV_34E9&SUBSYS_72708086&REV_30\3&11583659&0&A9 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_icl.inf_amd64_04e193b8806eca82\iaLPSS2_I2C.sys, 30.100.1916.0001 (English), 5/8/2019 01:59:22, 197008 bytes Name: Intel(R) USB 3.10 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_34ED&SUBSYS_72708086&REV_30\3&11583659&0&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.22000.0469 (English), 2/11/2022 12:19:38, 656744 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.22000.0469 (English), 2/11/2022 12:19:38, 161512 bytes Name: Intel(R) Wi-Fi 6 AX201 160MHz Device ID: PCI\VEN_8086&DEV_34F0&SUBSYS_00748086&REV_30\3&11583659&0&A3 Driver: C:\WINDOWS\system32\DRIVERS\Netwtw10.sys, 22.130.0000.0005 (English), 3/18/2022 05:15:22, 4874856 bytes Driver: C:\WINDOWS\system32\DRIVERS\Netwfw10.dat, 3/18/2022 05:15:22, 48759416 bytes Driver: C:\WINDOWS\system32\IntelIHVRouter08.dll, 22.12120.0000.0001 (English), 3/18/2022 05:15:22, 1626192 bytes Name: Intel(R) Precise Touch Device Device ID: PCI\VEN_8086&DEV_34E4&SUBSYS_00411414&REV_30\3&11583659&0&B4 Driver: C:\WINDOWS\system32\DRIVERS\iaPreciseTouch.sys, 2.01.0000.0059 (English), 8/3/2019 01:43:10, 795088 bytes Name: Intel(R) Serial IO UART Host Controller - 34A8 Device ID: PCI\VEN_8086&DEV_34A8&SUBSYS_72708086&REV_30\3&11583659&0&F0 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_uart2_icl.inf_amd64_2fd93d380196ad59\iaLPSS2_UART2.sys, 30.100.1932.0006 (English), 8/9/2019 19:27:36, 309648 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.22000.0120 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.22000.0120 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.22000.0653 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.22000.0001 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.22000.0001 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.22000.0653 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.22000.0120 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.22000.0653 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.22000.0653 DV Muxer,0x00400000,0,0,qdv.dll,10.00.22000.0653 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.22000.0001 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.22000.0653 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.22000.0001 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.22000.0001 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.22000.0653 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.22000.0675 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.22000.0653 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.22000.0653 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.22000.0001 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.22000.0001 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.22000.0001 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.22000.0653 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.22000.0653 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.22000.0653 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.22000.0653 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.22000.0653 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.22000.0001 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.22000.0001 DV Splitter,0x00600000,1,2,qdv.dll,10.00.22000.0653 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.22000.0001 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.22000.0653 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.22000.0001 Video Renderer,0x00800001,1,0,quartz.dll,10.00.22000.0001 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.22000.0653 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.22000.0001 Video Renderer,0x00400000,1,0,quartz.dll,10.00.22000.0001 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.22000.0653 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.22000.0653 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,10.00.22000.0653 File writer,0x00200000,1,0,qcap.dll,10.00.22000.0653 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.22000.0653 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.22000.0001 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.22000.0653 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.22000.0653 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.22000.0653 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.22000.0653 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.22000.0653 Null Renderer,0x00200000,1,0,qedit.dll,10.00.22000.0653 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.22000.0653 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.22000.0653 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.22000.0653 Smart Tee,0x00200000,1,2,qcap.dll,10.00.22000.0653 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.22000.0001 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.22000.0001 Wave Parser,0x00400000,1,1,quartz.dll,10.00.22000.0001 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.22000.0001 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.22000.0001 File stream renderer,0x00400000,1,1,quartz.dll,10.00.22000.0001 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.22000.0653 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.22000.0653 AVI Mux,0x00200000,1,0,qcap.dll,10.00.22000.0653 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.22000.0001 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.22000.0001 File Source (URL),0x00400000,0,1,quartz.dll,10.00.22000.0001 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.22000.0653 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.22000.0001 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.22000.0653 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.22000.0001 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.22000.0469 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.22000.0653 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.22000.0653 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.22000.0653 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.22000.0653 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.22000.0001 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.22000.0653 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.22000.0001 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.22000.0001 PCM,0x00200000,1,1,quartz.dll,10.00.22000.0001 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.22000.0001 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.22000.0001 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.22000.0001 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.22000.0001 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.22000.0001 Audio Capture Sources: Microphone Array (Realtek High Definition Audio(SST)),0x00200000,0,0,qcap.dll,10.00.22000.0653 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.22000.0653 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.22000.0653 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.22000.0653 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.22000.0001 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.22000.0001 WDM Streaming Capture Devices: ,0x00000000,0,0,, Headset Microphone,0x00200000,1,1,ksproxy.ax,10.00.22000.0469 ,0x00000000,0,0,, Realtek HD Audio Mic input with SST,0x00200000,1,3,ksproxy.ax,10.00.22000.0469 ,0x00000000,0,0,, ,0x00000000,0,0,, ,0x00000000,0,0,, ,0x00000000,0,0,, ,0x00000000,0,0,, Surface Camera Front,0x00200000,1,1,ksproxy.ax,10.00.22000.0469 WDM Streaming Rendering Devices: ,0x00200000,1,1,, ,0x00000000,0,0,, ,0x00000000,0,0,, ,0x00000000,0,0,, ,0x00200000,1,1,, ,0x00000000,0,0,, ,0x00200000,1,1,, ,0x00200000,1,1,, ,0x00200000,1,1,, Realtek HD Audio 2nd output with SST,0x00200000,2,2,ksproxy.ax,10.00.22000.0469 Realtek HD Audio output with SST,0x00200000,2,2,ksproxy.ax,10.00.22000.0469 ,0x00000000,0,0,, BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0653 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0653 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0653 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0653 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.22000.0653 Video Capture Sources: Surface Camera Front,0x00200000,1,1,ksproxy.ax,10.00.22000.0469 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.22000.0653 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.22000.0653 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.22000.0653 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.22000.0469 Audio Renderers: Speakers (Realtek High Definition Audio(SST)),0x00200000,1,0,quartz.dll,10.00.22000.0001 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.22000.0001 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.22000.0001 DirectSound: Speakers (Realtek High Definition Audio(SST)),0x00200000,1,0,quartz.dll,10.00.22000.0001 ---------------------------- 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.22000.0675 mfreadwrite.dll, 10.00.22000.0001 mfcaptureengine.dll, 10.00.22000.0653 mfsensorgroup.dll, 10.00.22000.0653 windows.media.dll, 10.00.22000.0653 frameserver.dll, 10.00.22000.0653 frameserverclient.dll, 10.00.22000.0653 --------------------------- 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.0004.0014 Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 11.21.0004.0014 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.22000.0675 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.22000.0653 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.22000.0001 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.22000.0675 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.22000.0653 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.22000.0120 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.22000.0653 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.22000.0653 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.22000.0653 MPEG2VideoExtension HEVCVideoExtension WebpImageExtension HEIFImageExtension VP9VideoExtensionDecoder Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 11.21.0004.0014 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 11.21.0004.0014 Intel� Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 11.21.0004.0014 Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 11.21.0004.0014 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 11.21.0004.0014 Intel� Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 11.21.0004.0014 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.22000.0348 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.22000.0653 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.22000.0653 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.22000.0653 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.22000.0653 HEVCVideoExtensionEncoder HEIFImageExtension VP9VideoExtensionEncoder Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.22000.0653 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.22000.0653 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.22000.0653 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.22000.0653 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.22000.0071 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.22000.0593 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.22000.0653 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.22000.0653 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.22000.0120 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.22000.0675 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.22000.0675 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.22000.0675 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.22000.0120 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.22000.0653 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.22000.0653 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.22000.0675 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.22000.0653 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.22000.0675 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.22000.0675 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.22000.0001 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.22000.0653 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.22000.0675 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.22000.0653 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.22000.0653 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.22000.0653 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.22000.0675 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.22000.0653 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.22000.0653 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.22000.0653 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.22000.0653 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.22000.0001 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.22000.0653 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.22000.0653 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.22000.0653 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.22000.0653 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.22000.0001 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.22000.0675 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.22000.0675 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableEncoders = 1 EnableDecoders = 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} {E06D8033-DB46-11CF-B4D1-00805F6CBBEA}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {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} {C2FE6F0A-4E3C-4DF1-9B60-50863091E4B9}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} 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 2237894073032733516, type 5 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.LockApp_10.0.22000.1_neutral__cw5n1h2txyewy P2: praid:runtimebroker07f4358a809ac99a64a67c1 P3: 10.0.22000.1 P4: 456ef38e P5: Windows.ApplicationModel.LockScreen.dll P6: 10.0.22000.1 P7: 43ea5f76 P8: c0000005 P9: 000000000000f669 P10: +++ WER1 +++: Fault bucket , type 0 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.LockApp_10.0.22000.1_neutral__cw5n1h2txyewy P2: praid:runtimebroker07f4358a809ac99a64a67c1 P3: 10.0.22000.1 P4: 456ef38e P5: Windows.ApplicationModel.LockScreen.dll P6: 10.0.22000.1 P7: 43ea5f76 P8: c0000005 P9: 000000000000f669 P10: +++ WER2 +++: Fault bucket , type 0 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.LockApp_10.0.22000.1_neutral__cw5n1h2txyewy P2: praid:runtimebroker07f4358a809ac99a64a67c1 P3: 10.0.22000.1 P4: 456ef38e P5: Windows.ApplicationModel.LockScreen.dll P6: 10.0.22000.1 P7: 43ea5f76 P8: c0000005 P9: 000000000000f669 P10: +++ WER3 +++: Fault bucket , type 0 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.LockApp_10.0.22000.1_neutral__cw5n1h2txyewy P2: praid:runtimebroker07f4358a809ac99a64a67c1 P3: 10.0.22000.1 P4: 456ef38e P5: Windows.ApplicationModel.LockScreen.dll P6: 10.0.22000.1 P7: 43ea5f76 P8: c0000005 P9: 000000000000f669 P10: +++ WER4 +++: Fault bucket , type 0 Event Name: RADAR_PRE_LEAK_WOW64 Response: Not available Cab Id: 0 Problem signature: P1: Zoom.exe P2: 5.10.4.5035 P3: 10.0.22000.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER5 +++: Fault bucket , type 0 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: dwm.exe P2: 10.0.22000.1 P3: 10.0.22000.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER6 +++: Fault bucket , type 0 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.LockApp_10.0.22000.1_neutral__cw5n1h2txyewy P2: praid:runtimebroker07f4358a809ac99a64a67c1 P3: 10.0.22000.1 P4: 456ef38e P5: Windows.ApplicationModel.LockScreen.dll P6: 10.0.22000.1 P7: 43ea5f76 P8: c0000005 P9: 000000000000f669 P10: +++ WER7 +++: Fault bucket , type 0 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: NortonSecurity.exe P2: 17.2.3.65 P3: 10.0.22000.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER8 +++: Fault bucket , type 0 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.LockApp_10.0.22000.1_neutral__cw5n1h2txyewy P2: praid:runtimebroker07f4358a809ac99a64a67c1 P3: 10.0.22000.1 P4: 456ef38e P5: Windows.ApplicationModel.LockScreen.dll P6: 10.0.22000.1 P7: 43ea5f76 P8: c0000005 P9: 000000000000f669 P10: +++ WER9 +++: Fault bucket , type 0 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.LockApp_10.0.22000.1_neutral__cw5n1h2txyewy P2: praid:runtimebroker07f4358a809ac99a64a67c1 P3: 10.0.22000.1 P4: 456ef38e P5: Windows.ApplicationModel.LockScreen.dll P6: 10.0.22000.1 P7: 43ea5f76 P8: c0000005 P9: 000000000000f669 P10: ...#SSU#...