# SSU Scan Information Scan Info: Version:"3.0.0.2" Date:"01/04/2024" Time:"00:01:51.3184523" # Scanned Hardware Computer: BaseBoard Manufacturer:"Dell Inc." BIOS Mode:"UEFI" BIOS Version/Date:"Dell Inc. 1.6.1 , 11/14/2019" CD or DVD:"Not Available" Embedded Controller Version:"255.255" Platform Role:"Mobile" Processor:"Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz , GenuineIntel" Secure Boot State:"Off" SMBIOS Version:"3.2" Sound Card:"Realtek Audio" Sound Card:"Realtek USB Audio" Sound Card:"Intel(R) Display Audio" System Manufacturer:"Dell Inc." System Model:"Latitude 7400" System SKU:"08E1" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"27.20.100.9313" - "Intel(R) UHD Graphics 620" 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) UHD Graphics 620" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=UHD+Graphics+620" CoInstallers:"oem12.inf,iWHL_w10_DS,Internal,Intel(R) UHD Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmd64.sys" Driver Date:"08/24/2022 01:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdkmd64.sys" Driver Provider:"Intel Corporation" Driver Version:"31.0.101.2114" INF:"oem12.inf" INF Section:"iWHL_w10_DS" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\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:"11.X" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_3EA0&SUBSYS_08E11028&REV_02\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"60 Hz" Refresh Rate - Maximum:"75 Hz" Refresh Rate - Minimum:"59 Hz" Resolution:"1280 X 1024" Scan Mode:"Noninterlaced" Service Name:"igfx" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) UHD Graphics Family" - "Memory" Physical Memory (Available):"15.33 GB" Physical Memory (Installed):"24 GB" Physical Memory (Total):"23.82 GB" - "DIMM A" Capacity:"16 GB" Channel:"DIMM A" Configured Clock Speed:"2133 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"First position" Manufacturer:"80AD000080AD" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"HMA82GS6JJR8N-VK" Serial Number:"835E7538" Status:"Not Available" Type:"Synchronous" - "DIMM B" Capacity:"8 GB" Channel:"DIMM B" Configured Clock Speed:"2133 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Second position" Manufacturer:"80AD000080AD" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"HMA41GS6AFR8N-TF" Serial Number:"277F9753" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"1.6.1, DELL - 1072009" Caption:"Motherboard" - "Chipset":"I/O LPC Controller - 9D84 for Intel(R) 300 Series" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=I%2fO+LPC+Controller+++9D84+for++300+Series" Date:"11/14/2019 12:00 AM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"Dell Inc." Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"07WDVW" Serial Number:"/2KL4533/CNCMK0004Q047B/" Status:"OK" Version:"A01" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Fortinet SSL VPN Virtual Ethernet Adapter" Availability:"Running or Full Power" Caption:"Fortinet SSL VPN Virtual Ethernet Adapter" 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:"ftsvnic.sys" Driver Date:"03/03/2023 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\ftsvnic.sys" Driver Provider:"Fortinet Inc" Driver Version:"16.17.14.743" Index:"0004" INF:"oem258.inf" INF Section:"ftsvnic.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:"01/04/2024 01:19 PM" Location:"Not Available" MAC Address:"00:09:0F:AA:00:01" Manufacturer:"Fortinet Inc" Net Connection ID:"Ethernet 5" NetCfgInstanceId:"{5664DDDD-0FC1-49A8-A71F-2F19C4168F26}" PNP Device ID:"ROOT\NET\0002" 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:"Fortinet SSL VPN Virtual Ethernet Adapter" Service Name:"ftsvnic" Status:"Enabled" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: 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: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: VirtualBox NDIS6 Bridged Networking Driver: - "Fortinet Virtual Ethernet Adapter (NDIS 6.30)" Availability:"Running or Full Power" Caption:"Fortinet Virtual Ethernet Adapter (NDIS 6.30)" 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:"ftvnic.sys" Driver Date:"09/04/2020 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\ftvnic.sys" Driver Provider:"Fortinet" Driver Version:"2020.4.9.0" Index:"0002" INF:"oem47.inf" INF Section:"FTNT.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:"01/04/2024 01:19 PM" Location:"Not Available" MAC Address:"00:09:0F:FE:00:01" Manufacturer:"Fortinet" Net Connection ID:"Ethernet 2" NetCfgInstanceId:"{0D0770AD-6242-42D7-960D-9C01D45678D1}" 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:"Fortinet Virtual Ethernet Adapter (NDIS 6.30)" Service Name:"ft_vnic" Status:"Enabled" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: 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: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: VirtualBox NDIS6 Bridged Networking Driver: - "Hyper-V Virtual Ethernet Adapter" Availability:"Running or Full Power" Caption:"Hyper-V Virtual Ethernet Adapter" 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:"VmsProxyHNic.sys" Driver Date:"06/21/2006 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\VmsProxyHNic.sys" Driver Provider:"Microsoft" Driver Version:"10.0.19041.1" Index:"0007" INF:"wvms_mp_windows.inf" INF Section:"VMSMP.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"172.17.78.193;fe80::7453:b0cb:b860:fac8" IP Subnet:"255.255.255.240;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/04/2024 01:19 PM" Location:"Not Available" MAC Address:"00:15:5D:37:59:4D" Manufacturer:"Microsoft" Net Connection ID:"vEthernet (WSL)" NetCfgInstanceId:"{E368F1DA-8AB8-4579-809E-824E6C4C1542}" PNP Device ID:"ROOT\VMS_MP\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:"Hyper-V Virtual Ethernet Adapter" Service Name:"VMSNPXYMP" Status:"Enabled" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: 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: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: VirtualBox NDIS6 Bridged Networking Driver: - "Settings" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *IPsecOffloadV2:IPSec Offload:"Auth Header and ESP Enabled (3)" *JumboPacket:Jumbo Packet:"Disabled (1514)" *LsoV2IPv4:Large Send Offload Version 2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload Version 2 (IPv6):"Enabled (1)" *MaxRssProcessors:Maximum Number of RSS Processors:"8 (8)" *NetworkDirect:Network Direct (RDMA):"Disabled (0)" *NumRSSQueues:Maximum Number of RSS Queues:"8 (8)" *RscIPv4:Recv Segment Coalescing (IPv4):"Enabled (1)" *RscIPv6:Recv Segment Coalescing (IPv6):"Enabled (1)" *RSS:Receive Side Scaling:"Enabled (1)" *RssBaseProcNumber:RSS Base Processor Number:"0 (0)" *RssMaxProcNumber:Maximum RSS Processor Number:"63 (63)" *RSSProfile:RSS Profile:"Closest Processor Static (2)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" NetworkAddress:Network Address:"00-15-5d-37-59-4d (00-15-5d-37-59-4d)" - "Intel(R) Wireless-AC 9560 160MHz" Access Point:"90:b8:32:71:bf:65" Authentication:"WPA2-Enterprise" Availability:"Running or Full Power" - "Caption":"Intel(R) Wireless-AC 9560 160MHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Wireless+AC+9560+160MHz" Channel:"157" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Auto Connect" Default IP Gateway:"193.62.118.1" DHCP Enabled:"Yes" DHCP Lease Expires:"01/04/2024 01:35 PM" DHCP Lease Obtained:"01/04/2024 01:20 PM" DHCP Server:"148.79.162.23" Driver:"Netwtw08.sys" Driver Date:"09/03/2023 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\Netwtw08.sys" Driver Provider:"Intel" Driver Version:"22.200.2.1" Index:"0008" INF:"oem362.inf" INF Section:"Install_GEN_PSR_JfP_9560_AC_2x2" Install Date:"Not Available" Installed:"Yes" IP Address:"193.62.118.140;fe80::8b29:2076:e214:889d" IP Subnet:"255.255.254.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/04/2024 01:19 PM" Location:"PCI bus 0, device 20, function 3" MAC Address:"08:D2:3E:1F:7F:84" Manufacturer:"Intel Corporation" Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{676FD236-4C44-4984-B594-70C02C5E66A8}" Network Name:"eduroam" Network Type:"Infrastructure" PNP Device ID:"PCI\VEN_8086&DEV_9DF0&SUBSYS_40308086&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: Yes" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Wireless-AC 9560 160MHz" Profile:"eduroam" Radio Type:"802.11ac" Receive Rate:"173.3 Mbps" Service Name:"Netwtw08" Signal Strength:"88%" State:"connected" Status:"Enabled" Transmit Rate:"173.3 Mbps" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: 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: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: VirtualBox NDIS6 Bridged Networking Driver: - "Settings" *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)" *PacketCoalescing:Packet Coalescing:"Enabled (1)" *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)" *PMNSOffload:NS offload for WoWLAN:"Enabled (1)" *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"Auto (1)" CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)" FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)" IbssTxPower:Transmit Power:"5. Highest (100)" IEEE11nMode:802.11n/ac Wireless Mode:"3. 802.11ac (2)" MIMOPowerSaveMode:MIMO Power Save Mode:"Auto SMPS (0)" RoamAggressiveness:Roaming Aggressiveness:"5. Highest (4)" RoamingPreferredBandType:Preferred Band:"3. Prefer 5GHz band (2)" ThroughputBoosterEnabled:Throughput Booster:"Enabled (1)" uAPSDSupport:U-APSD support:"Disabled (0)" WirelessMode:802.11a/b/g Wireless Mode:"6. Dual Band 802.11a/b/g (34)" - "Intel(R) Xeon Phi(TM) Virtual Ethernet Adapter (x64)" Availability:"Running or Full Power" - "Caption":"Intel(R) Xeon Phi(TM) Virtual Ethernet Adapter (x64)" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Xeon+Phi+Virtual+Ethernet+Adapter+(x64)" 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:"micvethx64.sys" Driver Date:"04/16/2013 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\micvethx64.sys" Driver Provider:"Intel Corporation" Driver Version:"6720.12.0.0" ETrackID:"Not Available" Index:"0001" INF:"oem62.inf" INF Section:"micvethx64.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:"01/04/2024 01:19 PM" Location:"Not Available" MAC Address:"Not Available" Manufacturer:"Intel Corporation" Net Connection ID:"Ethernet" NetCfgInstanceId:"{975AA111-BF65-488C-B079-E0A1320A8220}" NVM Version:"Not Available" Part Number:"Not Available" PNP Device ID:"ROOT\NET\0001" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Xeon Phi(TM) Virtual Ethernet Adapter (x64)" Service Name:"micvethx64" Status:"Not Available" Type:"Not Available" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: 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: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: VirtualBox NDIS6 Bridged Networking Driver: - "Realtek USB GbE Family Controller #3" Availability:"Running or Full Power" Caption:"Realtek USB GbE Family Controller #3" 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:"rtump64x64.sys" Driver Date:"08/06/2022 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\rtump64x64.sys" Driver Provider:"Realtek" Driver Version:"10.54.608.2022" Index:"0022" INF:"oem122.inf" INF Section:"RTL8153BCx64_Dis_SS_Hide_S5Wol_Dis_1mA.ndi.NT" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/04/2024 01:19 PM" Location:"Port_#0004.Hub_#0003" MAC Address:"C0:3E:BA:92:91:A3" Manufacturer:"Realtek" Net Connection ID:"Ethernet 6" NetCfgInstanceId:"{70752114-A14D-4F0D-86CB-277096CB1B7B}" PNP Device ID:"USB\VID_0BDA&PID_8153\111000001" 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: Yes" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Realtek USB GbE Family Controller" Service Name:"rtump64x64" Status:"Enabled" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: 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: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: VirtualBox NDIS6 Bridged Networking Driver: - "Settings" *EEE:Energy-Efficient Ethernet:"Enabled (1)" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Frame:"Disabled (1514)" *LsoV2IPv4:Large Send Offload v2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload v2 (IPv6):"Enabled (1)" *ModernStandbyWoLMagicPacket:Modern Standby WoL Magic Packet:"Disabled (0)" *PMARPOffload:ARP Offload:"Enabled (1)" *PMNSOffload:NS Offload:"Enabled (1)" *PriorityVLANTag:Priority & VLAN:"Priority & VLAN Enabled (3)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on pattern match:"Enabled (1)" AdvancedEEE:Advanced EEE:"Disabled (0)" BatteryModeLinkSpeed:Battery Mode Link Speed:"Not Speed Down (0)" EnableAdaptiveLinkCap:Adaptive Link Speed:"Disabled (0)" EnableExtraPowerSaving:Idle Power Saving:"Enabled (1)" EnableExtraTransmissionParm:Miscellaneous Transfer Settings:"Enabled (1)" EnableGreenEthernet:Green Ethernet:"Enabled (1)" S5WakeOnLan:Shutdown Wake-On-Lan:"Enabled (1)" WakeOnLinkChange:Wake on link change:"Enabled (1)" WolShutdownLinkSpeed:WOL & Shutdown Link Speed:"10 Mbps First (0)" - "VirtualBox Host-Only Ethernet Adapter" Availability:"Running or Full Power" Caption:"VirtualBox Host-Only Ethernet Adapter" 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:"VBoxNetAdp6.sys" Driver Date:"12/10/2023 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\VBoxNetAdp6.sys" Driver Provider:"Oracle Corporation" Driver Version:"7.0.12.9484" Index:"0003" INF:"oem90.inf" INF Section:"VBoxNetAdp6.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.56.1;fe80::ff94:7e35:7ae4:afaa" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/04/2024 01:19 PM" Location:"Not Available" MAC Address:"0A:00:27:00:00:05" Manufacturer:"Oracle Corporation" Net Connection ID:"VirtualBox Host-Only Network" NetCfgInstanceId:"{1EB8D0D9-7354-472D-86F1-696070A854BC}" PNP Device ID:"ROOT\NET\0003" 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:"VirtualBox Host-Only Ethernet Adapter" Service Name:"VBoxNetAdp" Status:"Enabled" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: FortiClient NDIS 6.3 Packet Filter Driver: 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: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: VirtualBox NDIS6 Bridged Networking Driver: - "Operating System" .Net Framework Version:"2.0,3.0,3.5,4.0,4.8" Boot Device:"\Device\HarddiskVolume1" Internet Browser:"Google Chrome,120.0, Internet Explorer,11.3636, Microsoft Edge,120.0" Locale:"United States" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Enterprise" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"3.50 GB" Physical Memory (Available):"15.37 GB" Physical Memory (Installed):"24 GB" Physical Memory (Total):"23.82 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.19045 Build 19045" Virtual Memory (Available):"17.99 GB" Virtual Memory (Total):"27.32 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [13/04/2023]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [13/04/2023]" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB5003791:"Update [10/6/2021]" KB5005699:"Security Update [10/6/2021]" KB5011048:"Update [12/5/2022]" KB5012170:"Security Update [12/15/2022]" KB5014032:"Security Update [11/22/2022]" KB5015684:"Update [8/10/2023]" KB5018506:"Update [11/23/2022]" KB5020372:"Update [1/3/2023]" KB5020613:"Update [11/23/2022]" KB5022924:"Update [3/20/2023]" KB5023319:"Update [2/3/2023]" KB5023794:"Update [4/13/2023]" KB5025315:"Update [5/16/2023]" KB5026879:"Update [6/16/2023]" KB5028318:"Update [7/13/2023]" KB5028380:"Update [8/11/2023]" KB5029709:"Update [9/18/2023]" KB5031539:"Update [10/12/2023]" KB5032005:"Update [11/24/2023]" KB5032392:"Update [11/22/2023]" KB5032907:"Update [1/2/2024]" KB5033372:"Security Update [1/3/2024]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [13/04/2023]" Microsoft .NET 6.0.12 - Windows Server Hosting (x86):".NET [11/01/2023]" Microsoft ASP.NET Core 6.0.24 - Shared Framework (x86):".NET [08/11/2023]" Microsoft ASP.NET Core 6.0.25 - Shared Framework (x64):".NET [24/11/2023]" SP1:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [Not Available]" - "Processor" - "Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 142 Stepping 12" - "Chipset Name":"Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i7+8665U+CPU+" CPU Speed:"1.91 GHz" Current Voltage:"8. volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.19041.3636" Ext. Family:"Not Available" Family:"Intel Core™ i7-2760QM" 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 256 KB" Level 2 Cache:"4 x 1024 KB" Level 3 Cache:"8 MB" Load:"100%" Manufacturer:"GenuineIntel" Model:"142" Name:"Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz" Number of Cores:"4" Number of Cores Enabled:"4" Number of Logical Processors:"8" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000806EC" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"12" Version:"Not Available" - "Storage" - "PM981a NVMe Samsung 512GB" Capablities:"Random Access, Supports Writing" Caption:"PM981a NVMe Samsung 512GB" Cylinder - Total:"62260" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.19041.3636" Error Code:"Device is working properly" Firmware Revision:"15302129" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"PM981a NVMe Samsung 512GB" Name:"\\.\PHYSICALDRIVE0" Partitions:"3" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_PM981A_NVME_SAMS\5&23FE03C0&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:"1000206900" Serial Number:"3447_5430_4E30_7839_0025_3846_0000_0001." Size:"476.94 GB" Size – Available:"28.93 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"15876300" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Windows" Serial Number:"78C22055" Size:"471.56 GB" Size – Available:"28.99 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Bootmgr failed to unseal VMK using the TPM ------------------------------------------------------------------- A corruption was discovered in the file system structure on volume F:. A file system index structure contains entries that violate ordering rules. The file reference number is 0x2000000002da3. The name of the file is "\System Volume Information". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION". The corrupted subtree is rooted at entry number 0 of the index block located at Vcn 0x4. ------------------------------------------------------------------- The shadow copy of volume F: could not create shadow copy storage on volume F:. ------------------------------------------------------------------- A corruption was discovered in the file system structure on volume F:. The exact nature of the corruption is unknown. The file system structures need to be scanned online. ------------------------------------------------------------------- Volume F: (\Device\HarddiskVolume7) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME " locally or remotely via PowerShell. ------------------------------------------------------------------- A corruption was discovered in the file system structure on volume F:. The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline. ------------------------------------------------------------------- The shadow copies of volume F: were aborted during detection. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3636.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register 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.AAD.BrokerPlugin_1000.19041.3636.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server MicrosoftWindows.Client.CBS_1000.19053.1000.0_x64__cw5n1h2txyewy!Global.IrisService.AppXwwah2tbqj7j749pkqvs0hna8en4npvp8.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.Search_1.14.10.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.3636_neutral_neutral_cw5n1h2txyewy!App.AppXryc2qd338f5728r9gzzazav8206ba77s.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server AD2F1837.HPPrinterControl_150.1.1140.0_x64__v10z8vjag6ke6!AD2F1837.HPPrinterControl.AppX3pygpm0xnrdftm5n1tftckhgsgz4zqvb.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.YourPhone_1.23102.126.0_x64__8wekyb3d8bbwe!App.AppX3vhsrrrr4az9vb3h5mjdzkhtshkg5v0x.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.WindowsFeedbackHub_1.2309.12711.0_x64__8wekyb3d8bbwe!App.AppX8a6w88secebzyje9nrqc47xt488tkbmc.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server MicrosoftWindows.Client.CBS_1000.19053.1000.0_x64__cw5n1h2txyewy!Global.IrisService.AppXwwah2tbqj7j749pkqvs0hna8en4npvp8.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server AD2F1837.HPPrinterControl_150.1.1140.0_x64__v10z8vjag6ke6!AD2F1837.HPPrinterControl.AppX3pygpm0xnrdftm5n1tftckhgsgz4zqvb.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3636.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel - Extension - 2252.71.74.0. ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to read the file \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to read the file \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel - Extension - 2252.71.74.0. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: ApplicationSet-9PB2MZ1ZMB1S-AppleInc.iTunes. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: ApplicationSet-9PB2MZ1ZMB1S-AppleInc.iTunes. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 21:39:57 on ‎18/‎12/‎2023 was unexpected. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel - Extension - 2252.71.74.0. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: Intel - Extension - 2252.71.74.0. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: ApplicationSet-9PB2MZ1ZMB1S-AppleInc.iTunes. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 15:59:35 on ‎11/‎12/‎2023 was unexpected. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "1E4131CC8882" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "1E4131CC8882" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 18:26:27 on ‎07/‎12/‎2023 was unexpected. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel - Extension - 2252.71.74.0. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- An attempt to configure the input mode of a multitouch device failed. ------------------------------------------------------------------- An attempt to configure the input mode of a multitouch device failed. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Bootmgr failed to unseal VMK using the TPM ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not evaluate the Windows Management Instrumentation (WMI) filter for the Group Policy object cn={4B1BE003-5603-45BD-A62A-04713091D319},cn=policies,cn=system,DC=fed,DC=cclrc,DC=ac,DC=uk. This could be caused by RSOP being disabled or Windows Management Instrumentation (WMI) service being disabled, stopped, or other WMI errors. Make sure the WMI service is started and the startup type is set to automatic. New Group Policy objects or settings will not process until this event has been resolved. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel - Extension - 2252.71.74.0. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 14:50:42 on ‎01/‎12/‎2023 was unexpected. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 15:10:32 on ‎27/‎11/‎2023 was unexpected. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The XTU3SERVICE service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the XTU3SERVICE service to connect. ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The AppXSvc service depends on the StateRepository service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The Wcmsvc service terminated with the following error: Not enough memory resources are available to process this command. ------------------------------------------------------------------- The Audiosrv service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Audiosrv service was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 17:45:30 on ‎24/‎11/‎2023 was unexpected. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- The shadow copies of volume G: were aborted during detection. ------------------------------------------------------------------- The default transaction resource manager on volume F: encountered a non-retryable error and could not start. The data contains the error code. ------------------------------------------------------------------- Unexpected failure. Error code: C000000E@020A0007 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: C000000E@020A0007 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: C000000E@020A0007 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- Unexpected failure. Error code: 1B1@01010013 ------------------------------------------------------------------- The shadow copies of volume G: were aborted during detection. ------------------------------------------------------------------- The shadow copies of volume G: were aborted during detection because a critical control file could not be opened. ------------------------------------------------------------------- The default transaction resource manager on volume F: encountered a non-retryable error and could not start. The data contains the error code. ------------------------------------------------------------------- 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 G: were aborted during detection because a critical control file could not be opened. ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- Device responded with an error status. Status: ReaderCompletionUnknownMsgType ------------------------------------------------------------------- The default transaction resource manager on volume F: encountered a non-retryable error and could not start. The data contains the error code. ------------------------------------------------------------------- The AllJoyn Router 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 AllJoyn Router Service service to connect. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service McpManagementService with arguments "Unavailable" in order to run the server: {A9819296-E5B3-4E67-8226-5E72CE9E1FB7} ------------------------------------------------------------------- The McpManagementService 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 McpManagementService service to connect. ------------------------------------------------------------------- The Windows Camera Frame Server 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 Camera Frame Server service to connect. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "1E084D701257" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 "1E084D701257" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable 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 NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ManageEngine UEMS -Agent service. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3570.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3570.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3570.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3570.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3570.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3570.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3570.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3570.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ManageEngine UEMS -Agent service. ------------------------------------------------------------------- Intel(R) Wireless-AC 9560 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ManageEngine UEMS -Agent service. ------------------------------------------------------------------- Intel(R) Wireless-AC 9560 160MHz : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel - Extension - 2252.71.74.0. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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: 9PB1QWVW0R95-Microsoft.WindowsAppRuntime.1.4. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 18:27:18 on ‎16/‎11/‎2023 was unexpected. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel - Extension - 2252.71.74.0. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: a) Name Resolution failure on the current domain controller. b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\javaexceptions.bat ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\scripts\VPN\PROXY_VPN_LOOKUP.VBS ------------------------------------------------------------------- Logon script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\User Script Name: \\fed.cclrc.ac.uk\SYSVOL\fed.cclrc.ac.uk\scripts\OTHER\MAPPED_DRIVES.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_LAPTOP_POLICY_BitLocker_AD GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{2F8CEF67-4BBD-4819-9C60-D19414AE4699}\Machine Script Name: \\fed.cclrc.ac.uk\netlogon\ENCRYPTION\ENCRYPTION_CHECK.vbs ------------------------------------------------------------------- Startup script failed. GPO Name : CSD_BASE_POLICY GPO File System Path : \\fed.cclrc.ac.uk\SysVol\fed.cclrc.ac.uk\Policies\{6E21F3AD-EFE9-41BF-A1A7-824B45A24B95}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\scripts\LEGAL_NOTICE\LEGALNOTICE.VBS ------------------------------------------------------------------- Startup script failed. GPO Name : Default Domain Policy GPO File System Path : \\fed.cclrc.ac.uk\sysvol\fed.cclrc.ac.uk\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine Script Name: ServerStartup.bat ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The NetMsmqActivator service depends on the following service: msmq. This service might not be installed. ------------------------------------------------------------------- The Hardlock service failed to start due to the following error: This driver has been blocked from loading ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CLRC due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 23:24:58 on ‎14/‎11/‎2023 was unexpected. ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 1/4/2024, 13:22:52 Machine name: DLNLAB0001 Machine Id: {9EF3F629-4894-43FB-9EE8-303F9BC7F030} Operating System: Windows 10 Enterprise 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406) Language: English (Regional Setting: English) System Manufacturer: Dell Inc. System Model: Latitude 7400 BIOS: 1.6.1 (type: UEFI) Processor: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 CPUs), ~2.1GHz Memory: 24576MB RAM Available OS Memory: 24390MB RAM Page File: 9198MB used, 18775MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.0.8 DxDiag Version: 10.00.19041.3636 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: 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) UHD Graphics 620 Manufacturer: Intel Corporation Chip type: Intel(R) UHD Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_3EA0&SUBSYS_08E11028&REV_02 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: 12323 MB Dedicated Memory: 128 MB Shared Memory: 12195 MB Current Mode: 1280 x 1024 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Internal 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.150391,0.059570), White Point(0.313477,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: DELL P1914S Monitor Id: DELF049 Native Mode: 1280 x 1024(p) (60.020Hz) 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_d8bdffa26077ee9a\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd12umd64.dll Driver File Version: 31.00.0101.2114 (English) Driver Version: 31.0.101.2114 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.7 Hardware Scheduling: Supported:False Enabled:False Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported 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: 24/08/2022 00:00:00, 1760312 bytes WHQL Logo'd: n/a WHQL Date Stamp: n/a Device Identifier: {D7B78E66-7DE0-11CF-DA7B-8428ADC2D235} Vendor ID: 0x8086 Device ID: 0x3EA0 SubSys ID: 0x08E11028 Revision ID: 0x0002 Driver Strong Name: oem12.inf:5f63e5345b9625c8:iWHL_w10_DS:31.0.101.2114:PCI\VEN_8086&DEV_3EA0 Rank Of Driver: 00CF2001 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} {2364D06A-F67F-4186-AED0-62B99E1784F1} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {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: 1 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported Extension Drivers: Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_6ac17bb69ef7ac60\iigd_ext.inf Driver Version: 30.0.101.1338 Driver Date: 01/20/2022 Driver Provider: Intel Corporation Catalog Attributes: Universal:False Declarative:True Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_405aac8d991f79e2\iigd_ext.inf Driver Version: 27.20.100.9126 Driver Date: 12/23/2020 Driver Provider: Intel Corporation Catalog Attributes: Universal:N/A Declarative:True Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_acfed682a318135c\iigd_ext.inf Driver Version: 26.20.100.8141 Driver Date: 04/11/2020 Driver Provider: Intel Corporation Catalog Attributes: Universal:N/A Declarative:True Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_5c160b15facf42e7\iigd_ext.inf Driver Version: 25.20.100.6577 Driver Date: 02/07/2019 Driver Provider: Intel Corporation Catalog Attributes: Universal:False 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 ------------- Sound Devices ------------- Description: Speakers/Headphones (Realtek(R) Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0295&SUBSYS_102808E1&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: RTKVHD64.sys Driver Version: 6.0.9137.1 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 24/03/2021 00:00:00, 6437376 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Emulation Only Cap Flags: 0x0 Min/Max Sample Rate: 0, 0 Static/Strm HW Mix Bufs: 0, 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(R) Audio) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: RTKVHD64.sys Driver Version: 6.0.9137.1 (English) Driver Attributes: Final Retail Date and Size: 24/03/2021 00:00:00, 6437376 bytes Cap Flags: 0x0 Format Flags: 0x0 --------------------- Video Capture Devices Number of Devices: 1 --------------------- FriendlyName: Integrated Webcam Category: Camera SymbolicLink: \\?\usb#vid_0bda&pid_565a&mi_00#6&2752971c&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 Manufacturer: Microsoft HardwareID: USB\VID_0BDA&PID_565A&REV_8176&MI_00,USB\VID_0BDA&PID_565A&MI_00 DriverDesc: USB Video Device DriverProvider: Microsoft DriverVersion: 10.0.19041.3758 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: Integrated Webcam Parent: USB\VID_0BDA&PID_565A\200901010001 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: n/a 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 ProfileIDs: n/a ------------------- 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: USB Multimedia Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046E, 0x550F FF Driver: n/a Device Name: Intel(R) HID Event Filter Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x8087, 0x0A1E FF Driver: n/a Device Name: Intel(R) HID Event Filter Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x8087, 0x0A1E FF Driver: n/a Device Name: USB Multimedia Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046E, 0x550F FF Driver: n/a Device Name: Dell Universal Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x413C, 0x301C FF Driver: n/a Device Name: Dell Universal Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x413C, 0x301C FF Driver: n/a Device Name: Dell Universal Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x413C, 0x301C 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: Converted Portable Device Control device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0000 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0xCD97 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0xCD97 FF Driver: n/a Device Name: USB Multimedia Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046E, 0x550F FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x9DED | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 1/2/2024 15:15:27, 649192 bytes | +-+ Generic USB Hub | | Vendor/Product ID: 0x0BDA, 0x5487 | | Location: Port_#0001.Hub_#0001 | | Matching Device ID: USB\USB20_HUB | | Service: USBHUB3 | | Driver: USBHUB3.SYS, 1/2/2024 15:15:27, 649192 bytes | | | +-+ Generic USB Hub | | | Vendor/Product ID: 0x0BDA, 0x5413 | | | Location: Port_#0003.Hub_#0005 | | | Matching Device ID: USB\USB20_HUB | | | Service: USBHUB3 | | | Driver: USBHUB3.SYS, 1/2/2024 15:15:27, 649192 bytes | | | | | +-+ Generic USB Hub | | | | Vendor/Product ID: 0x046E, 0x5411 | | | | Location: Port_#0003.Hub_#0006 | | | | Matching Device ID: USB\USB20_HUB | | | | Service: USBHUB3 | | | | Driver: USBHUB3.SYS, 1/2/2024 15:15:27, 649192 bytes | | | | | | | +-+ USB Composite Device | | | | | Vendor/Product ID: 0x413C, 0x301C | | | | | Location: Port_#0002.Hub_#0007 | | | | | Matching Device ID: USB\COMPOSITE | | | | | Service: usbccgp | | | | | Driver: usbccgp.sys, 11/24/2023 15:38:33, 190440 bytes | | | | | | | | | +-+ USB Input Device | | | | | | Vendor/Product ID: 0x413C, 0x301C | | | | | | Location: 0000.0014.0000.001.003.003.002.000.000 | | | | | | Matching Device ID: USB\Class_03&SubClass_01 | | | | | | Service: HidUsb | | | | | | Driver: hidusb.sys, 11/24/2023 15:38:33, 44032 bytes | | | | | | Driver: hidclass.sys, 11/24/2023 15:38:33, 233472 bytes | | | | | | Driver: hidparse.sys, 11/24/2023 15:38:33, 46080 bytes | | | | | | | | | | | +-+ HID Keyboard Device | | | | | | | Vendor/Product ID: 0x413C, 0x301C | | | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | | | Service: kbdhid | | | | | | | Driver: kbdhid.sys, 12/7/2019 09:07:56, 46592 bytes | | | | | | | Driver: kbdclass.sys, 12/7/2019 09:07:56, 71480 bytes | | | | | | | | | | +-+ USB Input Device | | | | | | Vendor/Product ID: 0x413C, 0x301C | | | | | | Location: 0000.0014.0000.001.003.003.002.000.000 | | | | | | Matching Device ID: USB\Class_03&SubClass_01 | | | | | | Service: HidUsb | | | | | | Driver: hidusb.sys, 11/24/2023 15:38:33, 44032 bytes | | | | | | Driver: hidclass.sys, 11/24/2023 15:38:33, 233472 bytes | | | | | | Driver: hidparse.sys, 11/24/2023 15:38:33, 46080 bytes | | | | | | | | | | | +-+ HID-compliant mouse | | | | | | | Vendor/Product ID: 0x413C, 0x301C | | | | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | | | | Service: mouhid | | | | | | | Driver: mouhid.sys, 12/7/2019 09:07:56, 35328 bytes | | | | | | | Driver: mouclass.sys, 12/7/2019 09:07:56, 67600 bytes | | | | | | | | +-+ USB Composite Device | | | | | Vendor/Product ID: 0x046E, 0x550F | | | | | Location: Port_#0003.Hub_#0007 | | | | | Matching Device ID: USB\COMPOSITE | | | | | Service: usbccgp | | | | | Driver: usbccgp.sys, 11/24/2023 15:38:33, 190440 bytes | | | | | | | | | +-+ USB Input Device | | | | | | Vendor/Product ID: 0x046E, 0x550F | | | | | | Location: 0000.0014.0000.001.003.003.003.000.000 | | | | | | Matching Device ID: USB\Class_03&SubClass_01 | | | | | | Service: HidUsb | | | | | | Driver: hidusb.sys, 11/24/2023 15:38:33, 44032 bytes | | | | | | Driver: hidclass.sys, 11/24/2023 15:38:33, 233472 bytes | | | | | | Driver: hidparse.sys, 11/24/2023 15:38:33, 46080 bytes | | | | | | | | | | | +-+ HID Keyboard Device | | | | | | | Vendor/Product ID: 0x046E, 0x550F | | | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | | | Service: kbdhid | | | | | | | Driver: kbdhid.sys, 12/7/2019 09:07:56, 46592 bytes | | | | | | | Driver: kbdclass.sys, 12/7/2019 09:07:56, 71480 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + Standard PS/2 Keyboard | Matching Device ID: *PNP0303 | Service: i8042prt | Driver: i8042prt.sys, 12/7/2019 09:07:56, 118272 bytes | Driver: kbdclass.sys, 12/7/2019 09:07:56, 71480 bytes | + HID Keyboard Device | Vendor/Product ID: 0x045E, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 12/7/2019 09:07:56, 46592 bytes | Driver: kbdclass.sys, 12/7/2019 09:07:56, 71480 bytes | + HID-compliant mouse | Vendor/Product ID: 0x06CB, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 12/7/2019 09:07:56, 35328 bytes | Driver: mouclass.sys, 12/7/2019 09:07:56, 67600 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 29.6 GB Total Space: 482.9 GB File System: NTFS Model: PM981a NVMe Samsung 512GB -------------- System Devices -------------- Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15DA&SUBSYS_08E11028&REV_02\6F7A4CA857B3020010 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:26, 478688 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15DA&SUBSYS_08E11028&REV_02\6F7A4CA857B3020008 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:26, 478688 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15DA&SUBSYS_08E11028&REV_02\6F7A4CA857B3020000 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:26, 478688 bytes Name: Intel(R) Serial IO I2C Host Controller - 9DE9 Device ID: PCI\VEN_8086&DEV_9DE9&SUBSYS_08E11028&REV_30\3&11583659&0&A9 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_cnl.inf_amd64_666eecf21665eb26\iaLPSS2_I2C_CNL.sys, 30.100.2020.0007 (English), 5/14/2020 23:42:42, 196360 bytes Name: Intel(R) Dynamic Tuning Processor Participant Device ID: PCI\VEN_8086&DEV_1903&SUBSYS_08E11028&REV_0C\3&11583659&0&20 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\esif_lf.sys, 8.07.10802.26924 (English), 4/15/2022 08:19:38, 427176 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\dptf_cpu.sys, 8.07.10802.26924 (English), 4/15/2022 08:19:32, 77992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\esif_uf.exe, 8.07.10802.26924 (English), 4/15/2022 08:19:40, 2284200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\esif_umdf2.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:42, 1024680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\Dptf.dll, 8.07.10802.26924 (English), 4/15/2022 08:18:56, 2285224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyRfim.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:20, 755872 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyActive.dll, 8.07.10802.26924 (English), 4/15/2022 08:18:58, 766120 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyActive2.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:00, 929456 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyEnergyPerformanceOptimizer.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:06, 821936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyAdaptiveUserPresence.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:04, 1019048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyAdaptivePerformance.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:02, 1078960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyCritical.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:04, 744104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyIntelligentThermalManagement.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:08, 903336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyPassive.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:10, 1037480 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyPassive2.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:12, 1000104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyPid.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:14, 907432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyPowerBoss.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:14, 1269416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyVirtualSensor.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:24, 903328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyPowerShare.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:16, 895144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicyPowerShare2.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:18, 913064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\DptfPolicySystemConfiguration.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:24, 716968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\upe_wwan.dll, 8.07.10802.26924 (English), 4/15/2022 08:20:00, 138920 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\upe_wifi.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:58, 70320 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\upe_nvme.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:54, 117936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\upe_battery.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:46, 74920 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\upe_socwc.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:56, 229032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\upe_hwpf.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:50, 78000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\dptf_helper.exe, 8.07.10802.26924 (English), 4/15/2022 08:19:34, 554152 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\esif_cmp.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:36, 141992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\ipftcs.dll, 8.07.10802.26924 (English), 4/15/2022 08:19:44, 1643944 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\dsp.dv, 4/15/2022 08:08:44, 840010 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_c2c5b0e17a28a48f\ppm.dv, 4/15/2022 08:08:44, 7608 bytes Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_9DED&SUBSYS_08E11028&REV_30\3&11583659&0&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.3636 (English), 11/24/2023 15:38:34, 625536 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.3636 (English), 11/24/2023 15:38:34, 143136 bytes Name: Intel(R) Wireless-AC 9560 160MHz Device ID: PCI\VEN_8086&DEV_9DF0&SUBSYS_40308086&REV_30\3&11583659&0&A3 Driver: C:\WINDOWS\system32\DRIVERS\Netwtw08.sys, 21.80.0027.0001 (English), 3/15/2023 19:51:48, 8877680 bytes Driver: C:\WINDOWS\system32\DRIVERS\Netwfw08.dat, 3/15/2023 19:39:12, 2686148 bytes Driver: C:\WINDOWS\system32\IntelIHVRouter08.dll, 22.12200.0000.0002 (English), 3/15/2023 19:51:34, 1470576 bytes Name: Intel(R) Host Bridge/DRAM Registers - 3E34 Device ID: PCI\VEN_8086&DEV_3E34&SUBSYS_08E11028&REV_0C\3&11583659&0&00 Driver: n/a Name: Intel(R) UHD Graphics 620 Device ID: PCI\VEN_8086&DEV_3EA0&SUBSYS_08E11028&REV_02\3&11583659&0&10 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdkmd64.sys, 31.00.0101.2114 (English), 10/7/2022 13:31:56, 44233280 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iglhxs64.vp, 10/7/2022 13:15:54, 5988 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd10iumd64.dll, 31.00.0101.2114 (English), 10/7/2022 13:32:26, 689056 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd10um64gen11.dll, 31.00.0101.2114 (English), 10/7/2022 13:32:34, 7541656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd11dxva64.dll, 31.00.0101.2114 (English), 10/7/2022 13:33:24, 52158144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd12dxva64.dll, 31.00.0101.2114 (English), 10/7/2022 13:34:12, 52162864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd12umd64.dll, 31.00.0101.2114 (English), 10/7/2022 13:34:42, 148784 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd12um64kbl.dll, 10/7/2022 13:34:38, 10905952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd12um64icl.dll, 10/7/2022 13:34:32, 10967336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdgmm64.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:42, 4308904 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igfxcmrt64.dll, 31.00.0101.2114 (English), 10/7/2022 13:36:06, 222240 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igfx11cmrt64.dll, 31.00.0101.2114 (English), 10/7/2022 13:36:04, 225360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdumdim64.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:58, 1760312 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdail64.dll, 10/7/2022 13:31:42, 196016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd9dxva64.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:30, 51883584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iga64.dll, 31.00.0101.2114 (English), 10/7/2022 13:31:50, 2912624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igc64.dll, 31.00.0101.2114 (English), 10/7/2022 13:32:22, 59050992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\DnnlPlugin.dll, 10/7/2022 13:31:44, 16884080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\UniversalAdapter64.dll, 10/7/2022 13:39:00, 348776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\opencl-clang64.dll, 2.00.0009.0000 (English), 10/7/2022 13:38:58, 82863448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdfcl64.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:38, 1082352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdmd64.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:50, 5551032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdml64.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:54, 1245416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdde64.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:34, 425416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdinfo64.dll, 10/7/2022 13:35:46, 163376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdext64.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:38, 305600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd10iumd32.dll, 31.00.0101.2114 (English), 10/7/2022 13:32:24, 662840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd10um32gen11.dll, 31.00.0101.2114 (English), 10/7/2022 13:32:30, 7296768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd11dxva32.dll, 31.00.0101.2114 (English), 10/7/2022 13:32:58, 51069168 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd12dxva32.dll, 31.00.0101.2114 (English), 10/7/2022 13:33:48, 51046768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd12umd32.dll, 31.00.0101.2114 (English), 10/7/2022 13:34:40, 111680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd12um32kbl.dll, 10/7/2022 13:34:24, 10351864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd12um32icl.dll, 10/7/2022 13:34:18, 10421256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdgmm32.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:40, 3348144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdumdim32.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:54, 1576744 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdail32.dll, 10/7/2022 13:31:42, 159664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igd9dxva32.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:06, 50797224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igfxcmrt32.dll, 31.00.0101.2114 (English), 10/7/2022 13:36:04, 178408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igfx11cmrt32.dll, 31.00.0101.2114 (English), 10/7/2022 13:36:02, 180488 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iga32.dll, 31.00.0101.2114 (English), 10/7/2022 13:31:48, 2335760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igc32.dll, 31.00.0101.2114 (English), 10/7/2022 13:32:04, 50062024 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\UniversalAdapter32.dll, 10/7/2022 13:38:58, 292344 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\opencl-clang32.dll, 2.00.0009.0000 (English), 10/7/2022 13:38:36, 61490880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdfcl32.dll, 31.00.0101.2114 (English), 10/7/2022 13:31:44, 983472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdmd32.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:48, 4389048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdml32.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:52, 928576 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdde32.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:32, 349296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdinfo32.dll, 10/7/2022 13:35:44, 137688 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdext32.dll, 31.00.0101.2114 (English), 10/7/2022 13:35:36, 245464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libigd12dxva64.so, 10/7/2022 13:15:54, 34118592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libigd12umd64.so, 10/7/2022 13:15:54, 43208 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libigd12um64kbl.so, 10/7/2022 13:15:54, 4775480 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libigd12um64icl.so, 10/7/2022 13:15:54, 4909608 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libigc.so, 10/7/2022 13:15:54, 41968416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libLLVM-9.so, 10/7/2022 13:15:58, 38566232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libigdgmm.so.12, 10/7/2022 13:15:54, 2288248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libUniversalAdapter64.so, 10/7/2022 13:16:00, 505936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libigdfcl.so, 10/7/2022 13:15:54, 986832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libopencl-clang.so.9, 10/7/2022 13:16:00, 81366600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libwsl_compute_helper.so, 10/7/2022 13:16:00, 567376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iglhxo64.vp, 10/7/2022 13:15:54, 42513 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iglhxc64.vp, 10/7/2022 13:15:54, 44194 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iglhxg64.vp, 10/7/2022 13:15:54, 43760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iglhxo64_dev.vp, 10/7/2022 13:15:54, 43143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iglhxc64_dev.vp, 10/7/2022 13:15:54, 43214 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iglhxg64_dev.vp, 10/7/2022 13:15:54, 43732 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iglhxa64.vp, 10/7/2022 13:15:54, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\iglhxa64.cpa, 10/7/2022 13:15:54, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\IntelCpHDCPSvc.exe, 31.00.0101.2114 (English), 10/7/2022 13:32:48, 343080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\cp_resources.bin, 10/7/2022 13:15:52, 2572396 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\ig9icd64.dll, 31.00.0101.2114 (English), 10/7/2022 13:31:36, 17349584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\ig9icd32.dll, 31.00.0101.2114 (English), 10/7/2022 13:31:32, 13838288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\OSSCOPYRIGHT.txt, 10/7/2022 13:16:00, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igvk64.dll, 31.00.0101.2114 (English), 10/7/2022 13:36:30, 23595472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igvk64.json, 10/7/2022 13:15:54, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\VulkanRT-EULA.txt, 10/7/2022 13:16:00, 4008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igvk32.dll, 31.00.0101.2114 (English), 10/7/2022 13:36:18, 21641016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igvk32.json, 10/7/2022 13:15:54, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\vulkan-1-64.dll, 1.03.0204.0001 (English), 10/7/2022 13:34:06, 1432352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\vulkaninfo-64.exe, 1.03.0204.0001 (English), 10/7/2022 13:34:08, 1969704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\vulkan-1-32.dll, 1.03.0204.0001 (English), 10/7/2022 13:34:04, 1145632 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\vulkaninfo-32.exe, 1.03.0204.0001 (English), 10/7/2022 13:34:08, 1526360 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.03.0204.0001 (English), 10/7/2022 13:34:04, 1145632 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.03.0204.0001 (English), 10/7/2022 13:34:08, 1526360 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.03.0204.0001 (English), 10/7/2022 13:34:04, 1145632 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.03.0204.0001 (English), 10/7/2022 13:34:08, 1526360 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.03.0204.0001 (English), 10/7/2022 13:34:06, 1432352 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.03.0204.0001 (English), 10/7/2022 13:34:08, 1969704 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.03.0204.0001 (English), 10/7/2022 13:34:06, 1432352 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.03.0204.0001 (English), 10/7/2022 13:34:08, 1969704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 10/7/2022 13:32:54, 362912 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdrcl32.dll, 23.20.0101.2114 (English), 10/7/2022 13:32:10, 3753384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 10/7/2022 13:32:56, 500144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\ze_loader.dll, 1.08.0001.0000 (English), 10/7/2022 13:34:14, 382928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\ze_validation_layer.dll, 1.08.0001.0000 (English), 10/7/2022 13:34:18, 143784 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\ze_tracing_layer.dll, 1.08.0001.0000 (English), 10/7/2022 13:34:14, 477096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\igdrcl64.dll, 23.20.0101.2114 (English), 10/7/2022 13:32:12, 4305872 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\ze_intel_gpu64.dll, 1.03.0000.0000 (English), 10/7/2022 13:34:12, 4375504 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 2.02.0008.0000 (English), 10/7/2022 13:32:54, 362912 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 2.02.0008.0000 (English), 10/7/2022 13:32:56, 500144 bytes Driver: C:\WINDOWS\system32\ze_loader.dll, 1.08.0001.0000 (English), 10/7/2022 13:34:14, 382928 bytes Driver: C:\WINDOWS\system32\ze_validation_layer.dll, 1.08.0001.0000 (English), 10/7/2022 13:34:18, 143784 bytes Driver: C:\WINDOWS\system32\ze_tracing_layer.dll, 1.08.0001.0000 (English), 10/7/2022 13:34:14, 477096 bytes Driver: C:\WINDOWS\SysWow64\libmfxhw32.dll, 22.05.0019.0430 (English), 10/7/2022 13:37:28, 709272 bytes Driver: C:\WINDOWS\SysWow64\mfxplugin32_hw.dll, 22.05.0019.0430 (English), 10/7/2022 13:33:12, 20672424 bytes Driver: C:\WINDOWS\system32\libmfxhw64.dll, 22.05.0019.0430 (English), 10/7/2022 13:37:30, 948496 bytes Driver: C:\WINDOWS\system32\mfxplugin64_hw.dll, 22.05.0019.0430 (English), 10/7/2022 13:33:30, 27948464 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 22.05.0019.0430 (English), 10/7/2022 13:36:36, 594216 bytes Driver: C:\WINDOWS\system32\libvpl.dll, 2.06.0000.0000 (English), 10/7/2022 13:39:06, 514544 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 22.05.0019.0430 (English), 10/7/2022 13:36:38, 454480 bytes Driver: C:\WINDOWS\SysWow64\libvpl.dll, 2.06.0000.0000 (English), 10/7/2022 13:39:02, 455160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfxplugin64_hw.dll, 22.05.0019.0430 (English), 10/7/2022 13:33:30, 27948464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfxplugin64_av1e_gacc.dll, 3.11.0005.0020 (English), 10/7/2022 13:37:26, 12550272 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\intel_gfx_api-x64.dll, 22.05.0019.0430 (English), 10/7/2022 13:36:36, 594216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfxplugin32_hw.dll, 22.05.0019.0430 (English), 10/7/2022 13:33:12, 20672424 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfxplugin32_av1e_gacc.dll, 3.11.0005.0020 (English), 10/7/2022 13:37:20, 8609416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\intel_gfx_api-x86.dll, 22.05.0019.0430 (English), 10/7/2022 13:36:38, 454480 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_h264ve_32.dll, 22.05.0019.0430 (English), 10/7/2022 13:37:56, 2521416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_mjpgvd_32.dll, 22.05.0019.0430 (English), 10/7/2022 13:33:40, 2391464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_h265ve_32.dll, 22.05.0019.0430 (English), 10/7/2022 13:38:08, 2534384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_vp9ve_32.dll, 22.05.0019.0430 (English), 10/7/2022 13:38:18, 2529192 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_encrypt_32.dll, 22.05.0019.0430 (English), 10/7/2022 13:37:48, 2384264 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_av1hve_32.dll, 22.05.0019.0430 (English), 10/7/2022 13:37:34, 2530800 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\c_32.cpa, 10/7/2022 13:15:52, 1361159 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\cpa_32.vp, 10/7/2022 13:15:52, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\dev_32.vp, 10/7/2022 13:15:52, 57143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\he_32.vp, 10/7/2022 13:15:52, 75457 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mj_32.vp, 10/7/2022 13:16:00, 71013 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\h265e_32.vp, 10/7/2022 13:15:52, 77061 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\vp9e_32.vp, 10/7/2022 13:16:00, 76672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_av1hve_32.vp, 10/7/2022 13:16:00, 76697 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_h264ve_64.dll, 22.05.0019.0430 (English), 10/7/2022 13:38:02, 3069576 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_mjpgvd_64.dll, 22.05.0019.0430 (English), 10/7/2022 13:33:42, 2913712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_h265ve_64.dll, 22.05.0019.0430 (English), 10/7/2022 13:38:12, 3088360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_vp9ve_64.dll, 22.05.0019.0430 (English), 10/7/2022 13:38:20, 3083056 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_encrypt_64.dll, 22.05.0019.0430 (English), 10/7/2022 13:37:52, 2902272 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_av1hve_64.dll, 22.05.0019.0430 (English), 10/7/2022 13:37:42, 3084640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\c_64.cpa, 10/7/2022 13:15:52, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\cpa_64.vp, 10/7/2022 13:15:52, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\dev_64.vp, 10/7/2022 13:15:52, 56359 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\he_64.vp, 10/7/2022 13:15:52, 13227 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mj_64.vp, 10/7/2022 13:16:00, 12955 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\h265e_64.vp, 10/7/2022 13:15:52, 13815 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\vp9e_64.vp, 10/7/2022 13:16:00, 13646 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\mfx_mft_av1hve_64.vp, 10/7/2022 13:16:00, 13635 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libmfxhw64.dll, 22.05.0019.0430 (English), 10/7/2022 13:37:14, 28977888 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\libmfxhw32.dll, 22.05.0019.0430 (English), 10/7/2022 13:36:56, 27377304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\IntelCpHeciSvc.exe, 9.02.0001.0920 (English), 10/7/2022 13:32:50, 518704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\clangFEWrapper.dll, 10/7/2022 13:31:30, 33272512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_d8bdffa26077ee9a\clangFEWrapper32.dll, 10/7/2022 13:31:36, 26308176 bytes Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_15DB&SUBSYS_08E11028&REV_02\6F7A4CA857B3020000 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.3636 (English), 11/24/2023 15:38:34, 625536 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.3636 (English), 11/24/2023 15:38:34, 143136 bytes Name: PCI Express Upstream Switch Port Device ID: PCI\VEN_8086&DEV_15DA&SUBSYS_08E11028&REV_02\U6F7A4CA857B3020000 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:26, 478688 bytes Name: Intel(R) Serial IO I2C Host Controller - 9DEB Device ID: PCI\VEN_8086&DEV_9DEB&SUBSYS_08E11028&REV_30\3&11583659&0&AB Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_cnl.inf_amd64_666eecf21665eb26\iaLPSS2_I2C_CNL.sys, 30.100.2020.0007 (English), 5/14/2020 23:42:42, 196360 bytes Name: Intel(R) PCI Express Root Port #5 - 9DBC Device ID: PCI\VEN_8086&DEV_9DBC&SUBSYS_08E11028&REV_F0\3&11583659&0&E0 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:26, 478688 bytes Name: Intel(R) Serial IO I2C Host Controller - 9DC5 Device ID: PCI\VEN_8086&DEV_9DC5&SUBSYS_08E11028&REV_30\3&11583659&0&C8 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_cnl.inf_amd64_666eecf21665eb26\iaLPSS2_I2C_CNL.sys, 30.100.2020.0007 (English), 5/14/2020 23:42:42, 196360 bytes Name: Realtek PCIE CardReader Device ID: PCI\VEN_10EC&DEV_525A&SUBSYS_08E11028&REV_01\00000001004CE00000 Driver: C:\WINDOWS\system32\DRIVERS\RtsPer.sys, 10.00.17763.21313 (English), 5/15/2019 19:32:10, 975328 bytes Driver: C:\WINDOWS\SysWOW64\RsCRIcon.dll, 1.10.0000.0000 (English), 5/15/2019 19:32:08, 9943872 bytes Name: Intel(R) PCI Express Root Port #12 - 9DB3 Device ID: PCI\VEN_8086&DEV_9DB3&SUBSYS_08E11028&REV_F0\3&11583659&0&E8 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:26, 478688 bytes Name: Intel(R) SMBus - 9DA3 Device ID: PCI\VEN_8086&DEV_9DA3&SUBSYS_08E11028&REV_30\3&11583659&0&FC Driver: n/a Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_9DC8&SUBSYS_08E11028&REV_30\3&11583659&0&FB Driver: C:\WINDOWS\system32\DRIVERS\IntcAudioBus.sys, 10.23.0000.3349 (English), 3/10/2020 22:56:44, 292936 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:22, 97792 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:22, 388608 bytes Name: I/O LPC Controller - 9D84 for Intel(R) 300 Series Chipset Family On-Package Platform Controller Hub Device ID: PCI\VEN_8086&DEV_9D84&SUBSYS_08E11028&REV_30\3&11583659&0&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:25, 21480 bytes Name: Intel(R) Thermal Subsystem - 9DF9 Device ID: PCI\VEN_8086&DEV_9DF9&SUBSYS_08E11028&REV_30\3&11583659&0&90 Driver: n/a Name: Intel(R) Serial IO I2C Host Controller - 9DE8 Device ID: PCI\VEN_8086&DEV_9DE8&SUBSYS_08E11028&REV_30\3&11583659&0&A8 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_cnl.inf_amd64_666eecf21665eb26\iaLPSS2_I2C_CNL.sys, 30.100.2020.0007 (English), 5/14/2020 23:42:42, 196360 bytes Name: Thunderbolt(TM) Controller - 15D9 Device ID: PCI\VEN_8086&DEV_15D9&SUBSYS_08E11028&REV_02\6F7A4CA857B3020000 Driver: C:\WINDOWS\system32\DRIVERS\TbtBusDrv.sys, 1.41.1335.0000 (English), 6/29/2022 03:53:02, 3183200 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\TbtFilterDrv.dll, 1.41.1335.0000 (English), 6/29/2022 03:53:04, 287840 bytes Driver: C:\WINDOWS\TbtP2pShortcutService.exe, 1.41.1335.0000 (English), 6/29/2022 03:53:12, 256608 bytes Name: Standard NVM Express Controller Device ID: PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00\4&167CB8D7&0&00EC Driver: C:\WINDOWS\system32\DRIVERS\stornvme.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:32, 165248 bytes Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_9DE0&SUBSYS_08E11028&REV_30\3&11583659&0&B0 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\heci.inf_amd64_cf249bf95c3b8dcb\x64\TeeDriverW10x64.sys, 2306.04.0003.0000 (English), 2/27/2023 03:18:58, 320096 bytes Name: Intel(R) Gaussian Mixture Model - 1911 Device ID: PCI\VEN_8086&DEV_1911&SUBSYS_08E11028&REV_00\3&11583659&0&40 Driver: n/a Name: Intel(R) Active Management Technology - SOL (COM3) Device ID: PCI\VEN_8086&DEV_9DE3&SUBSYS_08E11028&REV_30\3&11583659&0&B3 Driver: C:\WINDOWS\system32\DRIVERS\serial.sys, 10.00.19041.0001 (English), 12/7/2019 09:07:54, 90624 bytes Name: Intel(R) PCI Express Root Port #13 - 9DB4 Device ID: PCI\VEN_8086&DEV_9DB4&SUBSYS_08E11028&REV_F0\3&11583659&0&EC Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/24/2023 15:38:26, 478688 bytes Name: Intel(R) SPI (flash) Controller - 9DA4 Device ID: PCI\VEN_8086&DEV_9DA4&SUBSYS_08E11028&REV_30\3&11583659&0&FD Driver: n/a Name: PCI standard RAM Controller Device ID: PCI\VEN_8086&DEV_9DEF&SUBSYS_08E11028&REV_30\3&11583659&0&A2 Driver: n/a ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.19041.3636 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.19041.3636 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.19041.0001 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.19041.0001 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.19041.3636 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.19041.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.19041.3636 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.19041.3636 MS ATC Screen Decoder 1,0x00600800,1,1,scdec.dll,16.00.4266.1001 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.19041.3636 DV Muxer,0x00400000,0,0,qdv.dll,10.00.19041.0001 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.19041.3636 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.19041.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.19041.3636 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.19041.3636 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.19041.3803 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.19041.3636 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.19041.0001 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.3636 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.19041.3636 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.3636 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.19041.3636 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.19041.0001 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.3636 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.19041.3636 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.19041.3636 DV Splitter,0x00600000,1,2,qdv.dll,10.00.19041.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.19041.3636 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.19041.3636 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.19041.3636 Video Renderer,0x00800001,1,0,quartz.dll,10.00.19041.3636 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.19041.0001 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.19041.3636 Video Renderer,0x00400000,1,0,quartz.dll,10.00.19041.3636 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.19041.0001 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.19041.0001 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax, File writer,0x00200000,1,0,qcap.dll,10.00.19041.0001 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.19041.3636 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.19041.3636 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.3636 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.19041.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.19041.3636 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.19041.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.19041.3636 Null Renderer,0x00200000,1,0,qedit.dll,10.00.19041.3636 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.19041.0001 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.19041.0001 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.19041.0001 Smart Tee,0x00200000,1,2,qcap.dll,10.00.19041.0001 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.3636 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.19041.3636 Wave Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 File stream renderer,0x00400000,1,1,quartz.dll,10.00.19041.3636 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.19041.3636 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.19041.0001 AVI Mux,0x00200000,1,0,qcap.dll,10.00.19041.0001 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.19041.3636 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.19041.3636 File Source (URL),0x00400000,0,1,quartz.dll,10.00.19041.3636 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.19041.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.19041.3636 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.19041.0001 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.19041.3636 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.19041.3636 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.19041.0001 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.19041.0001 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.19041.0001 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.19041.3636 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.19041.3636 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.19041.3636 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.3636 PCM,0x00200000,1,1,quartz.dll,10.00.19041.3636 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.3636 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.19041.3636 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.19041.3636 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.19041.3636 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.19041.3636 Audio Capture Sources: Microphone Array (Realtek(R) Audio),0x00200000,0,0,qcap.dll,10.00.19041.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.19041.3758 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.3758 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.3758 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.19041.3636 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.19041.3636 WDM Streaming Capture Devices: Realtek HD Audio Front Mic input,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 ,0x00000000,0,0,, Realtek HD Audio Mic input with SST,0x00200000,1,3,ksproxy.ax,10.00.19041.3636 Integrated Webcam,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Realtek USB Audio,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 WDM Streaming Rendering Devices: Realtek USB Audio,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Realtek USB Audio,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Realtek HD Audio output with SST,0x00200000,2,2,ksproxy.ax,10.00.19041.3636 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.19041.0001 Video Capture Sources: Integrated Webcam,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.3636 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.19041.0001 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.19041.0001 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Audio Renderers: Speakers/Headphones (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.19041.3636 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.19041.3636 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.19041.3636 DirectSound: Speakers/Headphones (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.19041.3636 ---------------------------- Preferred DirectShow Filters ---------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred] , [, ] MEDIASUBTYPE_DVD_LPCM_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_VIDEO, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS {78766964-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_mp4s, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {64697678-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {58564944-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {5634504D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_MP4S, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject {44495658-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVA, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mpg4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_h264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_H264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_WMV3, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_MP43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMV2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS2, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_M4S2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WVP2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_WMV1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS1, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_WVC1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_AVC1, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_MPEG_LOAS, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG_ADTS_AAC, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_WMAUDIO_LOSSLESS, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_WMAUDIO3, WMAudio Decoder DMO, CLSID_CWMADecMediaObject WMMEDIASUBTYPE_WMAudioV8, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS WMMEDIASUBTYPE_MP3, MP3 Decoder DMO, CLSID_CMP3DecMediaObject MEDIASUBTYPE_MPEG1Payload, MPEG Video Decoder, CLSID_CMpegVideoCodec MEDIASUBTYPE_MPEG1Packet, MPEG Video Decoder, CLSID_CMpegVideoCodec {6C737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64687664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MJPG, MJPEG Decompressor, CLSID_MjpegDec {20637664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MPEG1AudioPayload, MPEG Audio Decoder, CLSID_CMpegAudioCodec WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject WMMEDIASUBTYPE_WMSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject --------------------------- Media Foundation File Versions --------------------------- mfcore.dll, 10.00.19041.3803 mfreadwrite.dll, 10.00.19041.3636 mfcaptureengine.dll, 10.00.19041.3636 mfsensorgroup.dll, 10.00.19041.3636 windows.media.dll, 10.00.19041.3636 frameserver.dll, 10.00.19041.3636 frameserverclient.dll, 10.00.19041.3636 --------------------------- 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, 22.05.0019.0430 Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 22.05.0019.0430 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.19041.3803 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.19041.0001 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.19041.3636 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.19041.3803 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.19041.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.19041.3636 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.19041.3636 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.19041.3636 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.19041.3636 HEIFImageExtension VP9VideoExtensionDecoder WebpImageExtension AV1VideoExtension Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 22.05.0019.0430 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 22.05.0019.0430 Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 22.05.0019.0430 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 22.05.0019.0430 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.19041.3636 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.19041.3636 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.19041.0001 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.19041.0001 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.19041.3636 HEIFImageExtension VP9VideoExtensionEncoder Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.19041.3636 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.19041.3636 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.19041.3636 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.19041.3636 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.19041.3636 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.19041.3636 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.19041.3758 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.19041.0001 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.19041.3636 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.19041.3803 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.19041.3803 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.19041.3803 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.19041.3636 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.19041.3636 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.19041.3636 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.19041.3803 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.19041.0001 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.19041.3803 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.19041.3803 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.19041.0001 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.19041.3636 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.19041.3803 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.19041.3636 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.19041.3636 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.19041.3636 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.19041.3803 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.19041.3636 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.19041.3636 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.19041.0001 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.19041.3636 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.19041.3636 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.19041.0001 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.19041.3636 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.19041.0001 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.19041.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.19041.0001 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.19041.3636 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.19041.3803 -------------------------------------------- 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} {E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {A61AC364-AD0E-4744-89FF-213CE0DF8804}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {63616C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905} MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9} {00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} {0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A} {00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} {00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_ADTS, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B} {00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC} {00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE} KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514} {00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786} KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD} WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject ------------------------------------- Disabled Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\DoNotUse] ------------------------ Disabled Media Sources ------------------------ [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse] --------------- EVR Power Information --------------- Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0 --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: No Data +++ WER1 +++: No Data +++ WER2 +++: No Data +++ WER3 +++: No Data +++ WER4 +++: No Data +++ WER5 +++: No Data +++ WER6 +++: No Data +++ WER7 +++: No Data +++ WER8 +++: No Data +++ WER9 +++: No Data ...#SSU#...