# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"05/26/2021" Time:"00:00:48.8534656" # Scanned Hardware Computer: BaseBoard Manufacturer:"HP" BIOS Mode:"Legacy" BIOS Version/Date:"HP N82 Ver. 01.52 , 10/28/2020 12:00 AM" CD or DVD:"Not Available" Embedded Controller Version:"17.117" Platform Role:"Mobile" Processor:"Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz , GenuineIntel" Secure Boot State:"Not Available" SMBIOS Version:"2.7" Sound Card:"Intel(R) Display Audio" Sound Card:"HP Dock Audio" Sound Card:"USB Audio Device" Sound Card:"Conexant ISST Audio" System Manufacturer:"HP" System Model:"HP ZBook Studio G3" System SKU:"T6E10UT#ABA" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"1.7.125.0" - "Intel(R) HD Graphics 530" 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) HD Graphics 530" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=HD+Graphics+530" CoInstallers:"oem142.inf,iSKLD_w10_DS,Internal,Intel(R) HD Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmd64.sys" Driver Date:"10/13/2020 07:00 PM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdkmd64.sys" Driver Provider:"Intel Corporation" Driver Version:"27.20.100.8854" INF:"oem142.inf" INF Section:"iSKLD_w10_DS" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd12umd64.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 0, device 2, function 0" Manufacturer:"Intel Corporation" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_191B&SUBSYS_80D3103C&REV_06\3&11583659&2&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"60 Hz" Refresh Rate - Maximum:"60 Hz" Refresh Rate - Minimum:"60 Hz" Resolution:"1920 X 1080" Scan Mode:"Noninterlaced" Service Name:"igfx" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) HD Graphics Family" - "Memory" Physical Memory (Available):"10.17 GB" Physical Memory (Installed):"24 GB" Physical Memory (Total):"23.88 GB" - "ChannelA" Capacity:"8 GB" Channel:"Top-Slot 1(left)" Configured Clock Speed:"2133 MHz" Configured Voltage:"Not Available" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Noninterleaved" Manufacturer:"Hynix/Hyundai" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"HMA81GS6AFR8N-UH" Serial Number:"716FEB21" Status:"Not Available" Type:"Not Available" - "ChannelB" Capacity:"16 GB" Channel:"Top-Slot 2(right)" Configured Clock Speed:"2133 MHz" Configured Voltage:"Not Available" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"First position" Manufacturer:"Unknown - [0x9B85]" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"CT16G4SFD824A.C16FBD" Serial Number:"A323D56C" Status:"Not Available" Type:"Not Available" - "Motherboard" Availability:"Running or Full Power" BIOS:"Default System BIOS, HPQOEM - 0" Caption:"Motherboard" - "Chipset":"Intel(R) 100 Series/C230" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=100+Series%2fC230" Date:"10/27/2020 07:00 PM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"HP" Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"80D4" Serial Number:"PFPLNJ31T41AIK" Status:"OK" Version:"KBC Version 11.75" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"20.90.0.0" - "Broadcom NetXtreme Gigabit Ethernet" Availability:"Running or Full Power" Caption:"Broadcom NetXtreme Gigabit Ethernet" 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:"b57nd60a.sys" Driver Date:"04/06/2018 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\b57nd60a.sys" Driver Provider:"Microsoft" Driver Version:"214.0.0.0" Index:"0016" INF:"b57nd60a.inf" INF Section:"BCM57766_LHinst.NTamd64.6.1" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"05/05/2021 01:45 PM" Location:"PCI bus 61, device 0, function 0" MAC Address:"30:E1:71:EC:9F:E8" Manufacturer:"Broadcom" Media Type: Net Connection ID:"Ethernet 3" NetCfgInstanceId:"{34EF4718-47B2-4DA8-8256-1ACD0C67ABA6}" Number of VLANs:"0" PNP Device ID:"PCI\VEN_14E4&DEV_1682&SUBSYS_168214E4&REV_01\8&2B245A37&0&0008002000E4" 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:"Broadcom NetXtreme Gigabit Ethernet" Service Name:"b57nd60a" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: LiveQoS NDIS 6 Filter Driver: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Settings" *EEE:802.3az EEE:"Disable (0)" *FlowControl:Flow Control:"Auto Negotiation (4)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *JumboPacket:Jumbo Mtu:"1500 (1500)" *LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)" *NumRssQueues:Maximum Number of RSS Queues:"RSS 1 Queue (1)" *PMARPOffload:ARP Offload:"Enabled (1)" *PMNSOffload:NS Offload:"Enabled (1)" *PriorityVLANTag:Priority & VLAN:"Priority & VLAN Enabled (3)" *RSS:Receive Side Scaling:"Enabled (1)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPUDPChecksumOffloadIPv4:TCP/UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPUDPChecksumOffloadIPv6:TCP/UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" EeeCtrlMode:EEE Control Policies:"Optimal Power and Performance (1)" VlanID:VLAN ID:"0 (0)" WireSpeed:Ethernet@WireSpeed:"Enable (1)" WolSpeed:WOL Speed:"Lowest Speed Advertised (256)" - "Check Point Virtual Network Adapter For Endpoint VPN Client" Availability:"Running or Full Power" Caption:"Check Point Virtual Network Adapter For Endpoint VPN Client" CoInstallers:"vnaap_coinstall.dll, _vna_co_installer@16" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"vnaap.sys" Driver Date:"01/16/2017 12:00 AM" Driver Path:"C:\WINDOWS\system32\DRIVERS\vnaap.sys" Driver Provider:"Check Point" Driver Version:"1.2.0.3" Index:"0004" INF:"oem8.inf" INF Section:"VNA_Apollo.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"05/05/2021 01:45 PM" Location:"Not Available" MAC Address:"54:F9:CC:B1:77:04" Manufacturer:"Check Point" Media Type: Net Connection ID:"Ethernet" NetCfgInstanceId:"{DEFD26C9-76B4-4329-8730-664F3C74264F}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0000" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Check Point Virtual Network Adapter For Endpoint VPN Client" Service Name:"vna_ap" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: LiveQoS NDIS 6 Filter Driver: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Intel(R) Dual Band Wireless-AC 8260" Access Point:"c4:04:15:4a:28:b2" Authentication:"WPA2-Personal" Availability:"Running or Full Power" - "Caption":"Intel(R) Dual Band Wireless-AC 8260" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Dual+Band+Wireless+AC+8260" Channel:"153" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Auto Connect" Default IP Gateway:"192.168.99.1" DHCP Enabled:"Yes" DHCP Lease Expires:"05/27/2021 08:57 AM" DHCP Lease Obtained:"05/26/2021 08:57 AM" DHCP Server:"192.168.99.1" Driver:"Netwtw06.sys" Driver Date:"01/10/2021 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\Netwtw06.sys" Driver Provider:"Intel" Driver Version:"20.70.21.2" Index:"0001" INF:"oem148.inf" INF Section:"Install_MPCIEX_GENM2AENBT1_8260_AC_2x2_HMC_WINT_64_AC" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.99.17;fe80::e1fd:2b67:71b4:e024" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"05/05/2021 01:45 PM" Location:"PCI bus 1, device 0, function 0" MAC Address:"E4:A4:71:AD:28:6B" Manufacturer:"Intel Corporation" Media Type: Net Connection ID:"Wireless Network Connection" NetCfgInstanceId:"{49DF822B-DF70-463B-99BD-B78849EEC9A9}" Network Name:"NotYourDroid5G" Network Type:"Infrastructure" Number of VLANs:"0" PNP Device ID:"PCI\VEN_8086&DEV_24F3&SUBSYS_10108086&REV_3A\4&FBE94BF&0&00E0" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Dual Band Wireless-AC 8260" Profile:"NotYourDroid5G" Radio Type:"802.11ac" Receive Rate:"130 Mbps" Service Name:"Netwtw06" Signal Strength:"84%" State:"connected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate:"130 Mbps" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: LiveQoS NDIS 6 Filter Driver: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Settings" *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)" *PacketCoalescing:Packet Coalescing:"Enabled (1)" *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)" *PMNSOffload:NS offload for WoWLAN:"Enabled (1)" *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"Auto (1)" CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)" FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)" IbssTxPower:Transmit Power:"5. Highest (100)" IEEE11nMode:802.11n/ac Wireless Mode:"802.11ac (2)" MIMOPowerSaveMode:MIMO Power Save Mode:"Auto SMPS (0)" RoamAggressiveness:Roaming Aggressiveness:"3. Medium (2)" RoamingPreferredBandType:Preferred Band:"1. No Preference (0)" ThroughputBoosterEnabled:Throughput Booster:"Disabled (0)" uAPSDSupport:U-APSD support:"Disabled (0)" WirelessMode:802.11a/b/g Wireless Mode:"6. Dual Band 802.11a/b/g (34)" - "Intel(R) Ethernet Connection (2) I219-LM" Availability:"Running or Full Power" - "Caption":"Intel(R) Ethernet Connection (2) I219-LM" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Ethernet+Connection+(2)+I219+LM" 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:"e1d68x64.sys" Driver Date:"09/05/2019 12:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\e1d68x64.inf_amd64_b44028fc7fdf4fca\e1d68x64.sys" Driver Provider:"Intel" Driver Version:"12.18.9.11" ETrackID:"Not Available" Index:"0002" INF:"oem168.inf" INF Section:"E15B7.10.0.1.19H1" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"05/05/2021 01:45 PM" Location:"PCI bus 0, device 31, function 6" MAC Address:"98:E7:F4:DB:68:05" Manufacturer:"Intel" Media Type: Net Connection ID:"Local Area Connection" NetCfgInstanceId:"{8F11C512-653C-4307-BBAF-114A0B7B4713}" Number of VLANs:"0" NVM Version:"Not Available" Part Number:"FFFFFF-0FF" PNP Device ID:"PCI\VEN_8086&DEV_15B7&SUBSYS_80D4103C&REV_31\3&11583659&2&FE" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: Yes" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: Yes" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Ethernet Connection (2) I219-LM" Service Name:"e1dexpress" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: LiveQoS NDIS 6 Filter Driver: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Settings" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Packet:"Disabled (1514)" *LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)" *NumRssQueues:Maximum Number of RSS Queues:"2 Queues (2)" *PMARPOffload:Protocol ARP Offload:"Enabled (1)" *PMNSOffload:Protocol NS Offload:"Enabled (1)" *PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enabled (3)" *PtpHardwareTimestamp:PTP Hardware Timestamp:"Disabled (0)" *ReceiveBuffers:Receive Buffers:"256 (256)" *RSS:Receive Side Scaling:"Enabled (1)" *RSSProfile:RSS load balancing profile:"ClosestProcessor (1)" *SoftwareTimestamp:Software Timestamp:"Disabled (0)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *TransmitBuffers:Transmit Buffers:"512 (512)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" AdaptiveIFS:Adaptive Inter-Frame Spacing:"Disabled (0)" AutoPowerSaveModeEnabled:Link Speed Battery Saver:"Disabled (0)" EEELinkAdvertisement:Energy Efficient Ethernet:"On (1)" EnablePME:Enable PME:"Enabled (1)" ITR:Interrupt Moderation Rate:"Adaptive (65535)" LinkNegotiationProcess:Legacy Switch Compatibility Mode:"Disabled (1)" LogLinkStateEvent:Log Link State Event:"Enabled (51)" MasterSlave:Gigabit Master Slave Mode:"Auto Detect (0)" ReduceSpeedOnPowerDown:Reduce Speed On Power Down:"Enabled (1)" SipsEnabled:System Idle Power Saver:"Disabled (0)" ULPMode:Ultra Low Power Mode:"Enabled (1)" WaitAutoNegComplete:Wait for Link:"Auto Detect (2)" WakeOnLink:Wake on Link Settings:"Disabled (0)" - "Kerio Virtual Network Adapter" Availability:"Running or Full Power" Caption:"Kerio Virtual Network 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:"kvnet.sys" Driver Date:"01/03/2018 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\kvnet.sys" Driver Provider:"Kerio Technologies Inc." Driver Version:"9.3.0.2362" Index:"0006" INF:"oem111.inf" INF Section:"kvnet.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"05/05/2021 01:45 PM" Location:"Not Available" MAC Address:"44:45:53:54:4F:53" Manufacturer:"Kerio Technologies Inc." Media Type: Net Connection ID:"Kerio Virtual Network" NetCfgInstanceId:"{A2224EC1-EADF-4C20-A95C-178D8128686E}" Number of VLANs:"0" PNP Device ID:"ROOT\KVNETID\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:"Kerio Virtual Network Adapter" Service Name:"kvnet" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): - "PANGP Virtual Ethernet Adapter" Availability:"Running or Full Power" Caption:"PANGP 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:"pangpd.sys" Driver Date:"08/09/2010 12:00 AM" Driver Path:"C:\WINDOWS\system32\DRIVERS\pangpd.sys" Driver Provider:"PaloAltoNetworks" Driver Version:"3.0.1.4" Index:"0015" INF:"oem127.inf" INF Section:"PanGpd.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"05/05/2021 01:45 PM" Location:"Not Available" MAC Address:"02:50:41:00:00:01" Manufacturer:"PaloAltoNetworks" Media Type: Net Connection ID:"Ethernet 2" NetCfgInstanceId:"{4CF7632E-F62C-418C-A8CD-B84F728599FD}" Number of VLANs:"0" PNP Device ID:"ROOT\PANGPD\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:"PANGP Virtual Ethernet Adapter" Service Name:"PanGpd" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: LiveQoS NDIS 6 Filter Driver: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): QoS Packet Scheduler: - "Settings" MediaStatus:Media Status:"Application Controlled (0)" MTU:MTU:"1400 (1400)" PACKETS:PACKETS:"1024 (1024)" SPEED:SPEED:"2000 (2000)" - "Operating System" .Net Framework Version:"2.0,3.0,3.5,4.0,4.8" Boot Device:"\Device\HarddiskVolume1" Locale:"United States" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Pro" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"2.00 GB" Physical Memory (Available):"10.17 GB" Physical Memory (Installed):"24 GB" Physical Memory (Total):"23.88 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.18363 Build 18363" Virtual Memory (Available):"1.62 GB" Virtual Memory (Total):"25.88 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB4497165:"Update [6/29/2020]" KB4498523:"Security Update [6/12/2019]" KB4503308:"Security Update [6/12/2019]" KB4506933:"Security Update [7/4/2019]" KB4508433:"Security Update [8/14/2019]" KB4509096:"Security Update [7/10/2019]" KB4515383:"Security Update [9/11/2019]" KB4516115:"Security Update [9/12/2019]" KB4517245:"Update [2/18/2020]" KB4521863:"Security Update [10/11/2019]" KB4524569:"Security Update [11/15/2019]" KB4528759:"Security Update [1/16/2020]" KB4535680:"Security Update [1/14/2021]" KB4537759:"Security Update [2/17/2020]" KB4538674:"Security Update [2/14/2020]" KB4541338:"Security Update [3/12/2020]" KB4552152:"Security Update [4/17/2020]" KB4560959:"Security Update [6/10/2020]" KB4561600:"Security Update [6/11/2020]" KB4565554:"Security Update [7/16/2020]" KB4569073:"Security Update [8/12/2020]" KB4576751:"Security Update [9/10/2020]" KB4577586:"Update [2/22/2021]" KB4577670:"Security Update [10/14/2020]" KB4580325:"Security Update [10/14/2020]" KB4586863:"Security Update [11/11/2020]" KB4589211:"Update [4/5/2021]" KB4598479:"Security Update [1/14/2021]" KB4601395:"Security Update [3/8/2021]" KB4601556:"Update [3/1/2021]" KB5000908:"Security Update [3/22/2021]" KB5001337:"Security Update [4/18/2021]" KB5001406:"Security Update [4/14/2021]" - "Processor" - "Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 94 Stepping 3" - "Chipset Name":"Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i7+6700HQ+CPU+" CPU Speed:"2.59 GHz" Current Voltage:"1.7 volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.18362.1049" 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 128 KB" Level 2 Cache:"4 x 1024 KB" Level 3 Cache:"6 MB" Load:"8%" Manufacturer:"GenuineIntel" Model:"94" Name:"Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz" 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:"BFEBFBFF000506E3" Revision:"24067" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"3" Version:"Not Available" - "Storage" - "SAMSUNG MZNLN128HCGR-000 SCSI Disk Device" Capablities:"Random Access, Supports Writing, SMART Notification" Caption:"SAMSUNG MZNLN128HCGR-000 SCSI Disk Device" Cylinder - Total:"15566" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.18362.1350" Error Code:"Device is working properly" Firmware Revision:"EMT22H0Q" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"IDE" Manufacturer:"(Standard disk drives)" Model:"SAMSUNG MZNLN128HCGR-000 SCSI Disk Device" Name:"\\.\PHYSICALDRIVE0" Partitions:"4" Physical Sector Size:"512" PNP Device ID:"SCSI\DISK&VEN_SAMSUNG&PROD_MZNLN128HCGR-000\4&28509C0&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" Sectors - Per Track:"63" Sectors - Total:"250067790" Serial Number:"S206NXAH127455" Size:"119.24 GB" Size – Available:"20.96 GB" SMART Attributes:"Self-Test: 18 minutes, OK, Short Self-Test: 2 minutes, OK" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"3969330" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Windows" Serial Number:"3A84A74A" Size:"99.62 GB" Size – Available:"18.42 GB" Status:"Not Available" Volume Dirty:"No" - "D:" Availability:"Not Available" Caption:"D:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"HP_RECOVERY" Serial Number:"D4DFDFB0" Size:"16.61 GB" Size – Available:"1.69 GB" Status:"Not Available" Volume Dirty:"No" - "E:" Availability:"Not Available" Caption:"E:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"FAT32" Name:"HP_TOOLS" Serial Number:"CA74F567" Size:"1.99 GB" Size – Available:"0.84 GB" Status:"Not Available" Volume Dirty:"No" - "SMART" 0x01 Raw Read Error Rate:0:"2" 0x05 Reallocated Sector Count:0:"10" 0x09 Power-On Hours:4852:"1" 0x0B Calibration Retry Count:52:"1" 0x0C Power Cycle Count:623:"1" 0xAA Available Reserved Space:356:"10" 0xAB Program Fail Count:0:"10" 0xAC Erase Fail Count:0:"10" 0xAD Wear Leveling Count:105:"5" 0xAE Power-off Retract Count:52:"1" 0xB7 SATA Downshift Count:0:"1" 0xB8 End-to-End Error Detection Count:0:"97" 0xBB Uncorrectable Error Count:0:"0" 0xBC Reported Command Timeouts:66:"0" 0xBE Temperature - Current:42° C:"0" 0xBE Temperature - Highest:Not Available:"0" 0xBE Temperature - Lowest:Not Available:"40" 0xC4 Reallocation Count:0:"1" 0xC6 Uncorrectable Sector Count:0:"1" 0xC7 CRC Error Count:0:"1" - "Samsung Type-C USB Device" Capablities:"Random Access, Supports Writing, Supports Removable Media" Caption:"Samsung Type-C USB Device" Cylinder - Total:"31201" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.18362.1350" Error Code:"Device is working properly" Firmware Revision:"1100" Heads - Total:"255" Index:"1" INF:"disk.inf" Install Date:"Not Available" Interface Type:"USB" Manufacturer:"(Standard disk drives)" Model:"Samsung Type-C USB Device" Name:"\\.\PHYSICALDRIVE1" Partitions:"1" Physical Sector Size:"512" PNP Device ID:"USBSTOR\DISK&VEN_SAMSUNG&PROD_TYPE-C&REV_1100\0373120020010947&0" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" Sectors - Per Track:"63" Sectors - Total:"501244065" Serial Number:"AA00000000000489" Size:"239.01 GB" Size – Available:"226.55 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"7956255" - "F:" Availability:"Not Available" Caption:"F:" Compression Method:"Not Compressed" Description:"Removable Disk" File System:"NTFS" Name:"256G Duo" Serial Number:"828DF549" Size:"239.02 GB" Size – Available:"226.55 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 Microsoft Account Sign-in Assistant service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Microsoft Account Sign-in Assistant service to connect. ------------------------------------------------------------------- Unable to start a DCOM Server: Microsoft.Windows.ContentDeliveryManager_10.0.18362.449_neutral_neutral_cw5n1h2txyewy!App.AppXryc2qd338f5728r9gzzazav8206ba77s.mca as Unavailable/Unavailable. The error: "2147943855" Happened while starting this command: "C:\WINDOWS\system32\backgroundTaskHost.exe" -ServerName:App.AppXmtcan0h2tfbfy7k9kn8hbxb6dmzz1zh0.mca ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC1900104: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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 detected an address conflict for IP address 192.168.99.16 with the system having network hardware address 08-12-A5-E5-B8-91. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC1900104: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 driver detected a controller error on \Device\Harddisk1\DR9. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR9. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR9. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR9. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR9. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR9. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC1900104: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Windows Error Reporting Service service terminated with the following error: The paging file is too small for this operation to complete. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC1900104: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC1900104: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/10.97.65.247 failed to negotiate a common protocol version. The remote host offered version 2 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/10.25.35.170 failed to negotiate a common protocol version. The remote host offered version 2 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC1900104: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/10.25.35.130 failed to negotiate a common protocol version. The remote host offered version 2 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070643: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.339.94.0). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC19001E1: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff980377afb060, 0xffff8e0b30447c00, 0xffff98037f479d90). A dump was saved in: C:\WINDOWS\Minidump\050521-15375-01.dmp. Report Id: ce57ca07-7151-46cf-856d-d98b1aec1888. ------------------------------------------------------------------- The previous system shutdown at 11:58:47 PM on ‎5/‎4/‎2021 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffa988498ef060, 0xffffbd092e03f7b0, 0xffffa9885c60dc00). A dump was saved in: C:\WINDOWS\Minidump\050421-11578-01.dmp. Report Id: 9e0e4319-0796-4117-84e3-43079cd12aa8. ------------------------------------------------------------------- The previous system shutdown at 9:18:06 PM on ‎5/‎3/‎2021 was unexpected. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/10.25.35.19 failed to negotiate a common protocol version. The remote host offered version 3 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/10.25.35.130 failed to negotiate a common protocol version. The remote host offered version 2 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC19001E1: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffbf05a951a570, 0xffff950bf103f7b0, 0xffffbf05b4e489a0). A dump was saved in: C:\WINDOWS\Minidump\050121-11359-01.dmp. Report Id: 9d1ad68b-f420-49ef-b0c9-f25471bb1977. ------------------------------------------------------------------- The previous system shutdown at 10:42:22 PM on ‎4/‎30/‎2021 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- 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 INTERACT 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error: "2147942767" Happened while starting this command: C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683} ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC1900104: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/10.25.35.22 failed to negotiate a common protocol version. The remote host offered version 3 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Miniport Broadcom NetXtreme Gigabit Ethernet, {34ef4718-47b2-4da8-8256-1acd0c67aba6}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/10.25.35.22 failed to negotiate a common protocol version. The remote host offered version 3 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffcf084d2a2570, 0xffff94089fc3f7b0, 0xffffcf085831f010). A dump was saved in: C:\WINDOWS\Minidump\042821-16906-01.dmp. Report Id: 4c01022d-1013-4909-833a-765781644ac0. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 11:34:05 PM on ‎4/‎27/‎2021 was unexpected. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070643: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.337.69.0). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC1900104: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC19001E1: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC19001E1: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 INTERACT 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC1900104: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC19001E1: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error: "2147942767" Happened while starting this command: C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683} ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 10:36:18 AM on ‎4/‎9/‎2021 was unexpected. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x800704C7: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR2. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC19001E1: Feature update to Windows 10, version 20H2. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffa00ad6acd060, 0xffffb50d8486f7b0, 0xffffa00ae3012a20). A dump was saved in: C:\WINDOWS\Minidump\040121-13359-01.dmp. Report Id: 83c14f04-307f-44b9-b9d7-8b7f86b25c50. ------------------------------------------------------------------- The previous system shutdown at 10:23:51 PM on ‎3/‎31/‎2021 was unexpected. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR3. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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 INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-02 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5001028). ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 previous system shutdown at 4:26:39 PM on ‎3/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: Windows Malicious Software Removal Tool x64 - v5.87 (KB890830). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-02 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5001028). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-02 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5001028). ------------------------------------------------------------------- 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff810746313060, 0xfffffa85c9e3f7b0, 0xffff81075fc74010). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 48f29464-5dc8-4630-bd30-655b9be6586d. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 12:53:12 AM on ‎3/‎9/‎2021 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 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 INTERACT 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 8:58:33 AM on ‎3/‎8/‎2021 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- 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 0x80246007: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-02 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5001028). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024001E: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.331.2674.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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The event logging service encountered an error (res=112) while initializing logging resources for channel Microsoft-Windows-WER-Diag/Operational. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240031: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 4:30:52 PM on ‎3/‎5/‎2021 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240031: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240031: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffc60ef28b6060, 0xfffffb896ac6f7b0, 0xffffc60f0bd74010). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 516286a5-4e95-4de9-8393-06311a3f881c. ------------------------------------------------------------------- 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 INTERACT 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 9:59:42 PM on ‎3/‎1/‎2021 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error: "2147942767" Happened while starting this command: C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683} ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240031: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240031: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error: "2147942767" Happened while starting this command: C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683} ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-02 Cumulative Update Preview for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4601556). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240031: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240031: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240031: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Delivery Optimization service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070643: Windows Malicious Software Removal Tool x64 - v5.86 (KB890830). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/10.248.49.247 failed to negotiate a common protocol version. The remote host offered version 2 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240031: Intel Corporation - Display - 27.20.100.8854. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 crash dump file could not be created due to a lack of free space on the destination drive. Increasing the amount of free space on the destination drive may help prevent this error. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 11:14:52 PM on ‎2/‎5/‎2021 was unexpected. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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 system detected an address conflict for IP address 192.168.99.15 with the system having network hardware address 28-57-67-67-2B-FF. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 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 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 INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 system detected an address conflict for IP address 192.168.99.5 with the system having network hardware address 28-57-67-67-2B-FF. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error: "2147942767" Happened while starting this command: C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683} ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The AVG Antivirus service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has encountered an internal error and has failed. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has encountered a conflict in resources and could not load. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has encountered an internal error and has failed. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has encountered a conflict in resources and could not load. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The server {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has encountered an internal error and has failed. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has encountered a conflict in resources and could not load. ------------------------------------------------------------------- Intel(R) Dual Band Wireless-AC 8260 : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 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 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070070: 2021-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4598229). ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Miniport Broadcom NetXtreme Gigabit Ethernet, {34ef4718-47b2-4da8-8256-1acd0c67aba6}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- A CredSSP authentication to TERMSRV/10.248.49.247 failed to negotiate a common protocol version. The remote host offered version 2 which is not permitted by Encryption Oracle Remediation. See https://go.microsoft.com/fwlink/?linkid=866660 for more information. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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 INTERACT 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 {9AA46009-3CE0-458A-A354-715610A075E6} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- Miniport Broadcom NetXtreme Gigabit Ethernet, {34ef4718-47b2-4da8-8256-1acd0c67aba6}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 INTERACT 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 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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 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 INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Miniport Broadcom NetXtreme Gigabit Ethernet, {34ef4718-47b2-4da8-8256-1acd0c67aba6}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffdf8470f16060, 0xffffbc807406f7b0, 0xffffdf8482085c70). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 19c00566-ad84-4caa-b360-15776e0e9b67. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 5:56:37 PM on ‎12/‎21/‎2020 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- 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 INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffbc021e2b5060, 0xfffff88d9988f7b0, 0xffffbc022eb66010). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 4b910637-1684-4939-a2df-81b88b78a266. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 12:17:45 AM on ‎12/‎20/‎2020 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 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 INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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 {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- Miniport Broadcom NetXtreme Gigabit Ethernet, {34ef4718-47b2-4da8-8256-1acd0c67aba6}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Time service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The time service encountered an error and was forced to shut down. The error was: 0x8007045B: A system shutdown is in progress. ------------------------------------------------------------------- The Server service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 crash dump file could not be created due to a lack of free space on the destination drive. Increasing the amount of free space on the destination drive may help prevent this error. ------------------------------------------------------------------- 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 5:31:08 PM on ‎12/‎9/‎2020 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- Miniport Broadcom NetXtreme Gigabit Ethernet, {34ef4718-47b2-4da8-8256-1acd0c67aba6}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful. ------------------------------------------------------------------- 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffd785acea6060, 0xffffa5820286f7b0, 0xffffd785be1df010). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9bca8a38-65bb-47db-aff7-d0a340fcdc20. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 11:01:39 PM on ‎11/‎29/‎2020 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC0000001. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff930461461060, 0xffffb30bd868f7b0, 0xffff930471767900). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8465eddd-7f35-4a52-a7c0-8ba573cc4b24. ------------------------------------------------------------------- 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 INTERACT 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 10:21:49 AM on ‎11/‎23/‎2020 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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 {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff9e0233840060, 0xfffff804763cd7b0, 0xffff9e0240506720). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ed1b484f-4f65-4b0e-b7dc-bbc24101b76e. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 1:30:31 PM on ‎11/‎19/‎2020 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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 driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 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 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 INTERACT 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 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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 computer has rebooted from a bugcheck. The bugcheck was: 0x000000ca (0x0000000000000002, 0xffff838a71b369c0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 65f5ddcf-6097-41f7-966f-f9727315285a. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 2:49:02 PM on ‎11/‎16/‎2020 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 7:35:33 PM on ‎11/‎13/‎2020 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The Intel(R) Audio Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The AVG Antivirus service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- Miniport Broadcom NetXtreme Gigabit Ethernet, {34ef4718-47b2-4da8-8256-1acd0c67aba6}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 computer has rebooted from a bugcheck. The bugcheck was: 0x000000ca (0x0000000000000002, 0xffffbd843b3e9060, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: eac052b6-c6a7-45ba-b685-93abd14074e7. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 12:45:06 PM on ‎11/‎5/‎2020 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The Windows Push Notifications User Service_1a5e24 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server {0134A8B2-3407-4B45-AD25-E9F7C92A80BC} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {0134A8B2-3407-4B45-AD25-E9F7C92A80BC} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 5:39:51 PM on ‎11/‎3/‎2020 was unexpected. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {B9B05098-3E30-483F-87F7-027CA78DA287} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The DigitalPersona Authentication Service service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} 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 INTERACT 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. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ------------------------------------------------------------------- Miniport Broadcom NetXtreme Gigabit Ethernet, {34ef4718-47b2-4da8-8256-1acd0c67aba6}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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 {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error: "2147942767" Happened while starting this command: C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683} ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffdc83b28ee060, 0xfffff08fbc02f7b0, 0xffffdc83c2eb3010). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 1f3daf23-430e-4c3d-92a1-e565746ee335. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 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 system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The previous system shutdown at 7:03:27 PM on ‎10/‎26/‎2020 was unexpected. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- 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 INTERACT 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. ------------------------------------------------------------------- Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error: "2147942767" Happened while starting this command: C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683} ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain INTERACT 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 shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Check Point Virtual Network Adapter: Check Point Virtual Network Adapter: tried to release an unused adapter VNA4 ------------------------------------------------------------------- Check Point Virtual Network Adapter: [VNA4] ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 5/26/2021, 17:33:47 Machine name: II371-ZBOOK Machine Id: {E137FC71-C3E3-4A0B-A1BA-4440135389C2} Operating System: Windows 10 Pro 64-bit (10.0, Build 18363) (18362.19h1_release.190318-1202) Language: English (Regional Setting: English) System Manufacturer: HP System Model: HP ZBook Studio G3 BIOS: Default System BIOS (type: BIOS) Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 CPUs), ~2.6GHz Memory: 24576MB RAM Available OS Memory: 24456MB RAM Page File: 24892MB used, 1610MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: Unknown DxDiag Version: 10.00.18362.1500 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Display Tab 2: No problems found. Display Tab 3: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Sound Tab 3: No problems found. Sound Tab 4: No problems found. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: Intel(R) HD Graphics 530 Manufacturer: Intel Corporation Chip type: Intel(R) HD Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_191B&SUBSYS_80D3103C&REV_06 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: 12355 MB Dedicated Memory: 128 MB Shared Memory: 12227 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.639648,0.344727), Green(0.334961,0.625000), Blue(0.150391,0.051758), 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: unknown Monitor Id: LGD046F Native Mode: 1920 x 1080(p) (60.020Hz) Output Type: Internal Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd12umd64.dll Driver File Version: 27.20.0100.8854 (English) Driver Version: 27.20.100.8854 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.1 Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Not Supported Block List: No Blocks Catalog Attributes: Universal:False Declarative:False Driver Attributes: Final Retail Driver Date/Size: 10/13/2020 7:00:00 PM, 1471144 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-5A5B-11CF-1A51-B7A0BDC2D635} Vendor ID: 0x8086 Device ID: 0x191B SubSys ID: 0x80D3103C Revision ID: 0x0006 Driver Strong Name: oem142.inf:5f63e5340a14bf6c:iSKLD_w10_DS:27.20.100.8854:pci\ven_8086&dev_191b&subsys_80d3103c Rank Of Driver: 00D10001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 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 DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 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 Card name: Intel(R) HD Graphics 530 Manufacturer: Intel Corporation Chip type: Intel(R) HD Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_191B&SUBSYS_80D3103C&REV_06 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: 12355 MB Dedicated Memory: 128 MB Shared Memory: 12227 MB Current Mode: 1920 x 1080 (32 bit) (59Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.649414,0.337891), Green(0.289063,0.609375), Blue(0.146484,0.070313), 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: H243H Monitor Id: ACR0074 Native Mode: 1920 x 1080(p) (59.934Hz) 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\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd12umd64.dll Driver File Version: 27.20.0100.8854 (English) Driver Version: 27.20.100.8854 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.1 Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Not Supported Block List: No Blocks Catalog Attributes: Universal:False Declarative:False Driver Attributes: Final Retail Driver Date/Size: 10/13/2020 7:00:00 PM, 1471144 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-5A5B-11CF-1A51-B7A0BDC2D635} Vendor ID: 0x8086 Device ID: 0x191B SubSys ID: 0x80D3103C Revision ID: 0x0006 Driver Strong Name: oem142.inf:5f63e5340a14bf6c:iSKLD_w10_DS:27.20.100.8854:pci\ven_8086&dev_191b&subsys_80d3103c Rank Of Driver: 00D10001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 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 DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 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 Card name: Intel(R) HD Graphics 530 Manufacturer: Intel Corporation Chip type: Intel(R) HD Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_191B&SUBSYS_80D3103C&REV_06 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: 12355 MB Dedicated Memory: 128 MB Shared Memory: 12227 MB Current Mode: 1920 x 1080 (32 bit) (59Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.649414,0.337891), Green(0.289063,0.609375), Blue(0.146484,0.070313), 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: H243H Monitor Id: ACR0074 Native Mode: 1920 x 1080(p) (59.934Hz) 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\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd12umd64.dll Driver File Version: 27.20.0100.8854 (English) Driver Version: 27.20.100.8854 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.1 Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Not Supported Block List: No Blocks Catalog Attributes: Universal:False Declarative:False Driver Attributes: Final Retail Driver Date/Size: 10/13/2020 7:00:00 PM, 1471144 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-5A5B-11CF-1A51-B7A0BDC2D635} Vendor ID: 0x8086 Device ID: 0x191B SubSys ID: 0x80D3103C Revision ID: 0x0006 Driver Strong Name: oem142.inf:5f63e5340a14bf6c:iSKLD_w10_DS:27.20.100.8854:pci\ven_8086&dev_191b&subsys_80d3103c Rank Of Driver: 00D10001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 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 DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 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 ------------- Sound Devices ------------- Description: Speakers (2- Logitech USB Headset) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: USB\VID_046D&PID_0A44&REV_0127&MI_00 Manufacturer ID: 65535 Product ID: 65535 Type: WDM Driver Name: USBAUDIO.sys Driver Version: 10.00.18362.1474 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 3/21/2021 12:00:00 AM, 198656 bytes Other Files: Driver Provider: Microsoft HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No Description: H243H (Intel(R) Display Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: INTELAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101&REV_1000 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: IntcDAud.sys Driver Version: 10.26.0000.0009 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 12/3/2019 12:00:00 AM, 659488 bytes Other Files: Driver Provider: Intel(R) Corporation HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No Description: H243H (Intel(R) Display Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: INTELAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101&REV_1000 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: IntcDAud.sys Driver Version: 10.26.0000.0009 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 12/3/2019 12:00:00 AM, 659488 bytes Other Files: Driver Provider: Intel(R) Corporation HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No Description: Speakers (Conexant ISST Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: INTELAUDIO\FUNC_01&VEN_14F1&DEV_50F4&SUBSYS_103C80D3&REV_1001 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: CHDRT64ISST.sys Driver Version: 9.00.0232.0070 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 9/7/2020 12:00:00 AM, 2426744 bytes Other Files: Driver Provider: Conexant HW Accel Level: Basic Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- Description: Microphone (2- Logitech USB Headset) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: USBAUDIO.sys Driver Version: 10.00.18362.1474 (English) Driver Attributes: Final Retail Date and Size: 4/13/2021 21:48:38, 198656 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF Description: Internal Microphone (Conexant ISST Audio) Default Sound Capture: No Default Voice Capture: No Driver Name: CHDRT64ISST.sys Driver Version: 9.00.0232.0070 (English) Driver Attributes: Final Retail Date and Size: 11/13/2020 13:29:31, 2426744 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 1 --------------------- FriendlyName: HP HD Camera Category: Camera SymbolicLink: \\?\usb#vid_04f2&pid_b51d&mi_00#6&267ce47c&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 Manufacturer: Realtek HardwareID: USB\VID_04F2&PID_B51D&REV_9906&MI_00,USB\VID_04F2&PID_B51D&MI_00 DriverDesc: HP Universal Camera Driver DriverProvider: Realtek DriverVersion: 10.0.19041.20148 DriverDateEnglish: 6/22/2020 00:00:00 DriverDateLocalized: 6/22/2020 12:00:00 AM 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: HP HD Camera Parent: USB\VID_04F2&PID_B51D\200901010001 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \FileSystem\avgSnx,\FileSystem\avgSnx,\Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: Imaging SensorGroupID: {78DCB7D0-33EA-458B-B98A-56E9A3A40B50} MFT0: n/a DMFT: {09824200-9A44-4B06-8C74-92D99E09B435} CustomCaptureSource: n/a DependentStillCapture: n/a EnablePlatformDMFT: n/a DMFTChain: {09824200-9A44-4B06-8C74-92D99E09B435},{3D096DDE-8971-4AD5-98F9-C74F56492630} EnableDshowRedirection: False 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 Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x0461, 0x0010 FF Driver: n/a Device Name: HP Wireless Button Driver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x0001, 0x0001 FF Driver: n/a Device Name: Micr Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0745 FF Driver: n/a Device Name: AlpsAlpine HID-compliant device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x044E, 0x1212 FF Driver: n/a Device Name: Microsoft Hardware USB Mouse Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0745 FF Driver: n/a Device Name: Micr Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0745 FF Driver: n/a Device Name: Micr Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0745 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x044E, 0x120C FF Driver: n/a Device Name: Micr Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0745 FF Driver: n/a Device Name: USB Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x0461, 0x0010 FF Driver: n/a Device Name: HP Dock Audio Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x0572, 0x1804 FF Driver: n/a Device Name: Logitech USB Headset Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0x0A44 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0xA12F | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 5/13/2020 18:23:48, 634680 bytes | +-+ USB Composite Device | | Vendor/Product ID: 0x045E, 0x0745 | | Location: Port_#0001.Hub_#0001 | | Matching Device ID: USB\COMPOSITE | | Service: usbccgp | | Driver: usbccgp.sys, 10/17/2020 17:46:34, 183616 bytes | | | +-+ Microsoft Hardware USB Keyboard | | | Vendor/Product ID: 0x045E, 0x0745 | | | Location: 0000.0014.0000.001.000.000.000.000.000 | | | Matching Device ID: usb\vid_045e&pid_0745&mi_00 | | | Service: HidUsb | | | Driver: WirelessKB850NotificationService.exe, 5/14/2018 21:32:16, 176624 bytes | | | Driver: KeyboardNotification.exe, 5/14/2018 21:32:14, 477688 bytes | | | Driver: hidusb.sys, 6/11/2019 20:29:49, 45568 bytes | | | Driver: hidclass.sys, 6/11/2019 20:29:49, 211968 bytes | | | Driver: hidparse.sys, 6/11/2019 20:29:49, 46080 bytes | | | | | +-+ Wireless Keyboard Filter Device | | | | Vendor/Product ID: 0x045E, 0x0745 | | | | Matching Device ID: HID\VID_045E&PID_0745&MI_00 | | | | Upper Filters: WirelessKeyboardFilter | | | | Service: kbdhid | | | | Driver: WirelessKeyboardFilter.sys, 3/11/2018 22:43:42, 49336 bytes | | | | Driver: kbdhid.sys, 3/18/2019 23:43:43, 46592 bytes | | | | Driver: kbdclass.sys, 3/18/2019 23:43:43, 70968 bytes | | | | +-+ Microsoft Hardware USB Mouse | | | Vendor/Product ID: 0x045E, 0x0745 | | | Location: 0000.0014.0000.001.000.000.000.000.000 | | | Matching Device ID: usb\vid_045e&pid_0745&mi_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 6/11/2019 20:29:49, 45568 bytes | | | Driver: hidclass.sys, 6/11/2019 20:29:49, 211968 bytes | | | Driver: hidparse.sys, 6/11/2019 20:29:49, 46080 bytes | | | Driver: coin99ip.dll, 11/10/2015 12:03:14, 466728 bytes | | | | | +-+ HID-compliant mouse | | | | Vendor/Product ID: 0x045E, 0x0745 | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | Service: mouhid | | | | Driver: mouhid.sys, 3/18/2019 23:43:43, 35840 bytes | | | | Driver: mouclass.sys, 3/18/2019 23:43:43, 66872 bytes | + ASMedia USB Root Hub | Matching Device ID: USB\ASMEDIAUSBD_Hub&VER_0001001600330001 | Service: asmthub3 | Driver: asmthub3.sys, 2/6/2016 14:25:06, 150272 bytes | +-+ Generic USB Hub | | Vendor/Product ID: 0x174C, 0x2074 | | Location: Port_#0003.Hub_#0001 | | Matching Device ID: USB\ASMEDIAUSBD_Hub | | Service: asmthub3 | | Driver: asmthub3.sys, 2/6/2016 14:25:06, 150272 bytes | | | +-+ USB Composite Device | | | Vendor/Product ID: 0x0461, 0x0010 | | | Location: Port_#0004.Hub_#0003 | | | Matching Device ID: USB\COMPOSITE | | | Service: usbccgp | | | Driver: usbccgp.sys, 10/17/2020 17:46:34, 183616 bytes | | | | | +-+ USB Input Device | | | | Vendor/Product ID: 0x0461, 0x0010 | | | | Location: 003c.0000.0000.004.003.004.000.000.000 | | | | Matching Device ID: USB\Class_03&SubClass_01 | | | | Service: HidUsb | | | | Driver: hidusb.sys, 6/11/2019 20:29:49, 45568 bytes | | | | Driver: hidclass.sys, 6/11/2019 20:29:49, 211968 bytes | | | | Driver: hidparse.sys, 6/11/2019 20:29:49, 46080 bytes | | | | | | | +-+ HID Keyboard Device | | | | | Vendor/Product ID: 0x0461, 0x0010 | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | Service: kbdhid | | | | | Driver: kbdhid.sys, 3/18/2019 23:43:43, 46592 bytes | | | | | Driver: kbdclass.sys, 3/18/2019 23:43:43, 70968 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + Standard 101/102-Key or Microsoft Natural PS/2 Keyboard for HP Hotkey Support | Matching Device ID: ACPI\HPQ8002 | Upper Filters: HpqKbFiltr | Service: i8042prt | Driver: HpqKbFiltr.sys, 12/14/2020 07:34:58, 52296 bytes | Driver: i8042prt.sys, 3/18/2019 23:43:43, 119296 bytes | Driver: kbdclass.sys, 3/18/2019 23:43:43, 70968 bytes | + HID Keyboard Device | Vendor/Product ID: 0x044E, 0x1212 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 3/18/2019 23:43:43, 46592 bytes | Driver: kbdclass.sys, 3/18/2019 23:43:43, 70968 bytes | + HID-compliant mouse | Vendor/Product ID: 0x044E, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 3/18/2019 23:43:43, 35840 bytes | Driver: mouclass.sys, 3/18/2019 23:43:43, 66872 bytes | + PS/2 Compatible Mouse | Matching Device ID: *PNP0F13 | Service: i8042prt | Driver: mouclass.sys, 3/18/2019 23:43:43, 66872 bytes | Driver: i8042prt.sys, 3/18/2019 23:43:43, 119296 bytes | + HID-compliant mouse | Vendor/Product ID: 0x044E, 0x1212 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 3/18/2019 23:43:43, 35840 bytes | Driver: mouclass.sys, 3/18/2019 23:43:43, 66872 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 18.9 GB Total Space: 102.0 GB File System: NTFS Model: SAMSUNG MZNLN128HCGR-000 SCSI Disk Device Drive: D: Free Space: 1.7 GB Total Space: 17.0 GB File System: NTFS Model: SAMSUNG MZNLN128HCGR-000 SCSI Disk Device Drive: E: Free Space: 0.9 GB Total Space: 2.0 GB File System: FAT32 Model: SAMSUNG MZNLN128HCGR-000 SCSI Disk Device -------------- System Devices -------------- Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_11112222&REV_00\5&251F9448&0&2000E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: Intel(R) 100 Series/C230 Series Chipset Family LPC Controller (CM236) - A150 Device ID: PCI\VEN_8086&DEV_A150&SUBSYS_80D4103C&REV_31\3&11583659&2&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.18362.0267 (English), 8/14/2019 08:08:08, 19256 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_11112222&REV_00\4&184C14A0&0&00E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_11112222&REV_00\5&251F9448&0&0800E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #1 - A110 Device ID: PCI\VEN_8086&DEV_A110&SUBSYS_80D4103C&REV_F1\3&11583659&2&E0 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_822B103C&REV_00\7&312982A0&0&20002000E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_11112222&REV_00\5&251F9448&0&1000E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: Intel(R) Management Engine Interface Device ID: PCI\VEN_8086&DEV_A13A&SUBSYS_80D4103C&REV_31\3&11583659&2&B0 Driver: C:\WINDOWS\system32\DRIVERS\TeeDriverW8x64.sys, 2102.100.0000.1044 (English), 1/6/2021 03:36:08, 277408 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_822B103C&REV_00\6&5B7421E&0&002000E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_822B103C&REV_00\7&312982A0&0&18002000E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_11112222&REV_00\5&251F9448&0&0000E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_A170&SUBSYS_80D4103C&REV_31\3&11583659&2&FB Driver: C:\WINDOWS\system32\DRIVERS\IntcAudioBus.sys, 9.21.0000.3690 (English), 10/5/2020 09:05:29, 266768 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.18362.1316 (English), 3/15/2021 10:26:54, 98304 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.18362.1316 (English), 3/15/2021 10:26:54, 390144 bytes Name: Intel(R) 100 Series/C230 Series Chipset Family Thermal subsystem - A131 Device ID: PCI\VEN_8086&DEV_A131&SUBSYS_80D4103C&REV_31\3&11583659&2&A2 Driver: n/a Name: Intel(R) HD Graphics 530 Device ID: PCI\VEN_8086&DEV_191B&SUBSYS_80D3103C&REV_06\3&11583659&2&10 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdkmd64.sys, 27.20.0100.8854 (English), 11/11/2020 04:36:28, 27580696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iglhxs64.vp, 11/11/2020 03:17:36, 5556 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd64.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:50, 23170200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd11dxva64.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:02, 77702320 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd12dxva64.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:14, 77483096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd12umd64.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:18, 22260376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdgmm64.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:48, 2520000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxcmrt64.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:20, 222448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfx11cmrt64.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:16, 225632 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdumdim64.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:12, 1471144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdail64.dll, 11/11/2020 04:36:24, 201560 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd9dxva64.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:30, 77459528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iga64.dll, 11/11/2020 04:36:30, 2808328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igc64.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:38, 47336208 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\UniversalAdapter64.dll, 11/11/2020 04:39:42, 518264 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\opencl-clang64.dll, 2.00.0008.0000 (English), 11/11/2020 04:39:32, 78530104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdfcl64.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:44, 1021736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdmd64.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:02, 12267480 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdml64.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:06, 4341984 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdde64.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:36, 431128 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdinfo64.dll, 11/11/2020 04:37:56, 163712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdext64.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:40, 460152 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10idpp64.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:40, 153752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10iumd32.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:44, 19886664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd11dxva32.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:54, 76367912 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd12dxva32.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:10, 76168672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd12umd32.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:16, 22055920 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdgmm32.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:46, 1889696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdumdim32.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:08, 1307080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdail32.dll, 11/11/2020 04:36:20, 169816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd9dxva32.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:24, 76137720 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxcmrt32.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:18, 181432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfx11cmrt32.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:14, 183584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iga32.dll, 11/11/2020 04:36:26, 2257496 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igc32.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:34, 41391664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\UniversalAdapter32.dll, 11/11/2020 04:39:38, 420952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\opencl-clang32.dll, 2.00.0008.0000 (English), 11/11/2020 04:39:22, 58915280 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdfcl32.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:26, 953176 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdmd32.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:58, 9814896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdml32.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:04, 3280928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdde32.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:32, 354832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdinfo32.dll, 11/11/2020 04:37:52, 141968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdext32.dll, 27.20.0100.8854 (English), 11/11/2020 04:37:38, 363344 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igd10idpp32.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:40, 130992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iglhxo64.vp, 11/11/2020 03:17:36, 42513 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iglhxc64.vp, 11/11/2020 03:17:36, 44194 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iglhxg64.vp, 11/11/2020 03:17:36, 43760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iglhxo64_dev.vp, 11/11/2020 03:17:36, 43143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iglhxc64_dev.vp, 11/11/2020 03:17:36, 43214 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iglhxg64_dev.vp, 11/11/2020 03:17:36, 43732 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iglhxa64.vp, 11/11/2020 03:17:36, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\iglhxa64.cpa, 11/11/2020 03:17:36, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\IntelCpHDCPSvc.exe, 25.20.0100.8854 (English), 11/11/2020 04:37:12, 529672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\cp_resources.bin, 11/11/2020 03:17:20, 2415596 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\difx64.exe, 1.04.0006.0000 (English), 11/11/2020 04:35:56, 273688 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxDH.dll, 6.15.0100.8854 (English), 11/11/2020 04:36:44, 983896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxDI.dll, 6.15.0100.8854 (English), 11/11/2020 04:36:48, 425304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxLHM.dll, 6.15.0100.8854 (English), 11/11/2020 04:36:58, 2265928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxEM.exe, 6.15.0100.8854 (English), 11/11/2020 04:36:52, 896280 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxCUIServicePS.dll, 11/11/2020 04:36:42, 411992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxCUIService.exe, 6.15.0100.8854 (English), 11/11/2020 04:36:40, 407816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxDHLib.dll, 1.00.0000.0000 (Invariant Language), 11/11/2020 04:36:46, 123736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxLHMLib.dll, 1.00.0000.0000 (Invariant Language), 11/11/2020 04:37:00, 22344 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\GfxUIEx.exe, 6.15.0100.8854 (English), 11/11/2020 04:36:04, 514312 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\Gfxv4_0.exe, 8.15.0100.8854 (English), 11/11/2020 04:36:06, 1247512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\GfxResources.dll, 8.15.0100.8854 (English), 11/11/2020 04:36:02, 9335128 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\MetroIntelGenericUIFramework.dll, 1.00.0000.0000 (English), 11/11/2020 04:37:24, 645976 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxCPL.cpl, 11/11/2020 04:36:38, 294232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxDTCM.dll, 6.15.0100.8854 (English), 11/11/2020 04:36:50, 198488 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxext.exe, 6.15.0100.8854 (English), 11/11/2020 04:36:56, 353048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxexps.dll, 6.15.0010.3682 (English), 11/11/2020 04:38:22, 58712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\GfxDownloadWrapper.exe, 8.15.0100.8854 (English), 11/11/2020 04:35:58, 162584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxSDK.exe, 11/11/2020 04:37:02, 991496 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxSDKLib.dll, 1.00.0000.0000 (Invariant Language), 11/11/2020 04:37:04, 99656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\ColorImageEnhancement.wmv, 11/11/2020 03:17:20, 375173 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\ImageStabilization.wmv, 11/11/2020 03:17:36, 403671 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\FilmModeDetection.wmv, 11/11/2020 03:17:20, 641530 bytes Driver: C:\WINDOWS\system32\igfxCPL.cpl, 11/11/2020 04:36:38, 294232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igfxexps32.dll, 6.15.0010.3682 (English), 11/11/2020 04:36:54, 52560 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igvk64.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:28, 19231464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igvk64.json, 11/11/2020 03:17:36, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\VulkanRT-EULA.txt, 11/11/2020 03:17:40, 4008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igvk32.dll, 27.20.0100.8854 (English), 11/11/2020 04:38:26, 17415832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igvk32.json, 11/11/2020 03:17:36, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\vulkan-1-64.dll, 1.02.0148.0001 (English), 11/11/2020 04:37:48, 1096320 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\vulkaninfo-64.exe, 1.02.0148.0001 (English), 11/11/2020 04:37:52, 1790232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\vulkan-1-32.dll, 1.02.0148.0001 (English), 11/11/2020 04:37:44, 949376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\vulkaninfo-32.exe, 1.02.0148.0001 (English), 11/11/2020 04:37:50, 1386256 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.02.0148.0001 (English), 11/11/2020 04:37:48, 1096320 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.02.0148.0001 (English), 11/11/2020 04:37:52, 1790232 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.02.0148.0001 (English), 11/11/2020 04:37:48, 1096320 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.02.0148.0001 (English), 11/11/2020 04:37:52, 1790232 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.02.0148.0001 (English), 11/11/2020 04:37:44, 949376 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.02.0148.0001 (English), 11/11/2020 04:37:50, 1386256 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.02.0148.0001 (English), 11/11/2020 04:37:44, 949376 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.02.0148.0001 (English), 11/11/2020 04:37:50, 1386256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\OSSCOPYRIGHT, 11/11/2020 03:17:40, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\ig9icd64.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:14, 16521560 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\ig9icd32.dll, 27.20.0100.8854 (English), 11/11/2020 04:36:12, 13211984 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 11/11/2020 04:37:20, 370520 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdrcl32.dll, 23.20.0100.8854 (English), 11/11/2020 04:36:34, 4339024 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 11/11/2020 04:37:22, 507736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\ze_loader.dll, 1.00.0012.0000 (English), 11/11/2020 04:38:00, 427848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\ze_validation_layer.dll, 1.00.0012.0000 (English), 11/11/2020 04:38:02, 148824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igdrcl64.dll, 23.20.0100.8854 (English), 11/11/2020 04:36:36, 4945240 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\ze_intel_gpu64.dll, 11/11/2020 04:37:56, 4357464 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 2.02.0008.0000 (English), 11/11/2020 04:37:20, 370520 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 2.02.0008.0000 (English), 11/11/2020 04:37:22, 507736 bytes Driver: C:\WINDOWS\system32\ze_loader.dll, 1.00.0012.0000 (English), 11/11/2020 04:38:00, 427848 bytes Driver: C:\WINDOWS\system32\ze_validation_layer.dll, 1.00.0012.0000 (English), 11/11/2020 04:38:02, 148824 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw32.dll, 11/11/2020 04:38:48, 253936 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin32_hw.dll, 1.20.0009.0015 (English), 11/11/2020 04:37:26, 13520200 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw64.dll, 11/11/2020 04:38:50, 306032 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin64_hw.dll, 1.20.0009.0015 (English), 11/11/2020 04:37:30, 26677080 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:30, 171504 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:34, 146792 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:06, 3240320 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:37:40, 3044184 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:14, 3261960 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:18, 3254064 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:00, 3035456 bytes Driver: C:\Program Files\Intel\Media SDK\c_64.cpa, 11/21/2018 15:23:00, 1376256 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_64.vp, 11/11/2020 03:17:20, 1125 bytes Driver: C:\Program Files\Intel\Media SDK\dev_64.vp, 11/11/2020 03:17:20, 56359 bytes Driver: C:\Program Files\Intel\Media SDK\he_64.vp, 11/11/2020 03:17:22, 13661 bytes Driver: C:\Program Files\Intel\Media SDK\mj_64.vp, 11/11/2020 03:17:38, 13393 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_64.vp, 11/11/2020 03:17:22, 14249 bytes Driver: C:\Program Files\Intel\Media SDK\vp9e_64.vp, 11/11/2020 03:17:40, 14096 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:02, 2625504 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:37:36, 2463056 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:08, 2638632 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:16, 2632888 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:58, 2465752 bytes Driver: C:\Program Files\Intel\Media SDK\c_32.cpa, 11/21/2018 15:23:00, 1361159 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_32.vp, 11/11/2020 03:17:20, 1125 bytes Driver: C:\Program Files\Intel\Media SDK\dev_32.vp, 11/11/2020 03:17:20, 57143 bytes Driver: C:\Program Files\Intel\Media SDK\he_32.vp, 11/11/2020 03:17:22, 71553 bytes Driver: C:\Program Files\Intel\Media SDK\mj_32.vp, 11/11/2020 03:17:38, 66901 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_32.vp, 11/11/2020 03:17:22, 73141 bytes Driver: C:\Program Files\Intel\Media SDK\vp9e_32.vp, 11/11/2020 03:17:40, 72712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\libmfxhw64.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:42, 25487416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfxplugin64_hw.dll, 1.20.0009.0015 (English), 11/11/2020 04:37:30, 26677080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfxplugin64_av1e_gacc.dll, 11/11/2020 04:38:46, 8060624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\intel_gfx_api-x64.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:30, 171504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\libmfxhw32.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:38, 23997776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfxplugin32_hw.dll, 1.20.0009.0015 (English), 11/11/2020 04:37:26, 13520200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfxplugin32_av1e_gacc.dll, 11/11/2020 04:38:44, 6963856 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\intel_gfx_api-x86.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:34, 146792 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_h264ve_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:02, 2625504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_mjpgvd_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:37:36, 2463056 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_h265ve_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:08, 2638632 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_vp9ve_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:16, 2632888 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_encrypt_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:58, 2465752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_av1hve_32.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:52, 2636072 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\c_32.cpa, 11/11/2020 03:17:20, 1361159 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\cpa_32.vp, 11/11/2020 03:17:20, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\dev_32.vp, 11/11/2020 03:17:20, 57143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\he_32.vp, 11/11/2020 03:17:22, 71553 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mj_32.vp, 11/11/2020 03:17:38, 66901 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\h265e_32.vp, 11/11/2020 03:17:22, 73141 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\vp9e_32.vp, 11/11/2020 03:17:40, 72712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_av1hve_32.vp, 11/11/2020 03:17:38, 72825 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_h264ve_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:06, 3240320 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_mjpgvd_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:37:40, 3044184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_h265ve_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:14, 3261960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_vp9ve_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:18, 3254064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_encrypt_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:39:00, 3035456 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_av1hve_64.dll, 10.20.0009.0015 (English), 11/11/2020 04:38:56, 3256736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\c_64.cpa, 11/11/2020 03:17:20, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\cpa_64.vp, 11/11/2020 03:17:20, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\dev_64.vp, 11/11/2020 03:17:20, 56359 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\he_64.vp, 11/11/2020 03:17:22, 13661 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mj_64.vp, 11/11/2020 03:17:38, 13393 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\h265e_64.vp, 11/11/2020 03:17:22, 14249 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\vp9e_64.vp, 11/11/2020 03:17:40, 14096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\mfx_mft_av1hve_64.vp, 11/11/2020 03:17:38, 14085 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\IntelCpHeciSvc.exe, 9.01.0001.0920 (English), 11/11/2020 04:37:14, 513288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_e6daaea9afe1e6f6\igxpco64.dll, 1.03.0027.0000 (English), 11/11/2020 04:37:08, 234824 bytes Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_15B6&SUBSYS_822B103C&REV_00\8&1ADD530C&0&0020002000E4 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.18362.0900 (English), 6/10/2020 14:42:35, 531768 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.18362.0900 (English), 6/10/2020 14:42:35, 132256 bytes Name: Synaptics SMBus Driver Device ID: PCI\VEN_8086&DEV_A123&SUBSYS_80D4103C&REV_31\3&11583659&2&FC Driver: C:\WINDOWS\system32\DRIVERS\Smb_driver_Intel.sys, 19.05.0010.0020 (English), 7/5/2019 16:10:52, 56840 bytes Name: Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) Host Bridge/DRAM Registers - 1910 Device ID: PCI\VEN_8086&DEV_1910&SUBSYS_80D4103C&REV_07\3&11583659&2&00 Driver: n/a Name: Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft) Device ID: PCI\VEN_8086&DEV_A12F&SUBSYS_80D4103C&REV_31\3&11583659&2&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.18362.0900 (English), 6/10/2020 14:42:35, 531768 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.18362.0900 (English), 6/10/2020 14:42:35, 132256 bytes Name: Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #2 - A111 Device ID: PCI\VEN_8086&DEV_A111&SUBSYS_80D4103C&REV_F1\3&11583659&2&E1 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: Broadcom NetXtreme Gigabit Ethernet Device ID: PCI\VEN_14E4&DEV_1682&SUBSYS_168214E4&REV_01\8&2B245A37&0&0008002000E4 Driver: C:\WINDOWS\system32\DRIVERS\b57nd60a.sys, 214.00.0000.0000 (English), 3/18/2019 23:43:41, 527872 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_822B103C&REV_00\7&312982A0&0&00002000E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #5 - A114 Device ID: PCI\VEN_8086&DEV_A114&SUBSYS_80D4103C&REV_F1\3&11583659&2&E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: Intel(R) Serial IO I2C Host Controller - A160 Device ID: PCI\VEN_8086&DEV_A160&SUBSYS_80D4103C&REV_31\3&11583659&2&A8 Driver: C:\WINDOWS\system32\DRIVERS\iaLPSS2_I2C.sys, 30.100.1841.0002 (English), 7/5/2019 16:11:02, 190920 bytes Name: Intel(R) 100 Series/C230 Series Chipset Family PMC - A121 Device ID: PCI\VEN_8086&DEV_A121&SUBSYS_80D4103C&REV_31\3&11583659&2&FA Driver: n/a Name: Thunderbolt(TM) Controller - 1577 Device ID: PCI\VEN_8086&DEV_1577&SUBSYS_11112222&REV_00\6&930C58&0&000000E4 Driver: C:\WINDOWS\system32\DRIVERS\tbt100x.sys, 17.04.0078.0021 (English), 10/5/2020 09:10:15, 138384 bytes Driver: C:\Intel\Thunderbolt\setup.msi, 10/5/2020 09:10:15, 8798208 bytes Driver: C:\WINDOWS\system32\tbtcoinx_17_4_78_21.dll, 17.04.0078.0021 (English), 10/5/2020 09:10:15, 411792 bytes Name: Intel(R) Ethernet Connection (2) I219-LM Device ID: PCI\VEN_8086&DEV_15B7&SUBSYS_80D4103C&REV_31\3&11583659&2&FE Driver: C:\WINDOWS\System32\DriverStore\FileRepository\e1d68x64.inf_amd64_b44028fc7fdf4fca\e1d68x64.sys, 12.18.0009.0011 (English), 9/13/2019 04:40:00, 599920 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\e1d68x64.inf_amd64_b44028fc7fdf4fca\e1dmsg.dll, 10.00.0911.0001 (English), 9/13/2019 04:40:00, 119152 bytes Name: ASMedia USB3.0 eXtensible Host Controller Device ID: PCI\VEN_1B21&DEV_1142&SUBSYS_8190103C&REV_00\8&5AA039A&0&0000002000E4 Driver: C:\WINDOWS\system32\DRIVERS\asmtxhci.sys, 1.16.0033.0001 (English), 2/6/2016 14:25:08, 449792 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_822B103C&REV_00\7&312982A0&0&10002000E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller Device ID: PCI\VEN_8086&DEV_A102&SUBSYS_80D4103C&REV_31\3&11583659&2&B8 Driver: C:\WINDOWS\system32\DRIVERS\iaStorAC.sys, 15.09.0006.1044 (English), 7/5/2019 16:13:34, 906160 bytes Name: PCI-to-PCI Bridge Device ID: PCI\VEN_8086&DEV_1578&SUBSYS_822B103C&REV_00\7&312982A0&0&08002000E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.1350 (English), 3/15/2021 10:26:54, 435024 bytes Name: Intel(R) Dual Band Wireless-AC 8260 Device ID: PCI\VEN_8086&DEV_24F3&SUBSYS_10108086&REV_3A\4&FBE94BF&0&00E0 Driver: C:\WINDOWS\system32\DRIVERS\Netwtw06.sys, 20.70.0021.0002 (English), 5/20/2021 16:01:52, 8809328 bytes Driver: C:\WINDOWS\system32\DRIVERS\Netwfw06.dat, 5/20/2021 16:01:51, 2635224 bytes Driver: C:\WINDOWS\system32\IntelIHVRouter06.dll, 22.12030.0000.0001 (English), 5/20/2021 16:01:51, 1422192 bytes Name: Intel(R) Dynamic Platform and Thermal Framework Processor Participant Device ID: PCI\VEN_8086&DEV_1903&SUBSYS_80D4103C&REV_07\3&11583659&2&20 Driver: C:\WINDOWS\system32\DRIVERS\esif_lf.sys, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 402264 bytes Driver: C:\WINDOWS\system32\DRIVERS\dptf_cpu.sys, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 71000 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\esif_uf.exe, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 1855976 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\esif_umdf2.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 849416 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\Dptf.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 2224648 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyRfim.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 863752 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyActive.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 881160 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyActive2.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 1059848 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyAdaptivePerformance.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 1446408 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyCritical.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 824328 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyConfigTdp.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 834056 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPassive.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 1067016 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPassive2.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 1108488 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPid.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 1045512 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPowerBoss.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 1719304 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyVirtualSensor.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 1023496 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\DptfPolicyPowerShare.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 1022472 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\upe_wifi.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 65544 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\upe_nvme.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 87560 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\upe_battery.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 69128 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\dptf_helper.exe, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 408040 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\esif_cmp.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 134664 bytes Driver: C:\WINDOWS\system32\Intel\DPTF\esif_ws.dll, 8.04.11000.6436 (English), 7/5/2019 16:12:19, 226824 bytes Driver: C:\WINDOWS\ServiceProfiles\LocalService\AppData\Local\Intel\DPTF\dsp.dv, 7/5/2019 16:12:19, 689470 bytes Name: Realtek PCIE CardReader Device ID: PCI\VEN_10EC&DEV_525A&SUBSYS_80D4103C&REV_01\4&252DDD32&0&00E1 Driver: C:\WINDOWS\system32\DRIVERS\RtsPer.sys, 10.00.19041.21334 (English), 8/7/2020 04:20:50, 1409568 bytes Driver: C:\WINDOWS\SysWOW64\RsCRIcon.dll, 1.10.0000.0000 (English), 8/7/2020 04:20:48, 9969184 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.18362.1082 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.18362.1082 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.18362.0001 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.18362.0001 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.18362.1016 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.18362.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.18362.1500 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.18362.0001 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.18362.0001 DV Muxer,0x00400000,0,0,qdv.dll,10.00.18362.0001 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.18362.1316 LAV Splitter,0x00400001,1,1,LAVSplitter.ax,0.75.0000.0002 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.18362.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.18362.1316 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.18362.1316 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.18362.0001 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.18362.1500 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.18362.0900 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.18362.0001 XySubFilter,0x00200000,1,0,XySubFilter.dll,3.02.0000.0805 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.18362.1316 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.18362.1316 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.18362.1316 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.18362.1316 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.18362.0900 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.18362.0001 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.18362.0001 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.18362.0001 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.18362.1316 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.18362.1316 DV Splitter,0x00600000,1,2,qdv.dll,10.00.18362.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.18362.1316 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.18362.0001 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.18362.1316 XySubFilterAutoLoader,0x00200000,1,0,XySubFilter.dll,3.02.0000.0805 Video Renderer,0x00800001,1,0,quartz.dll,10.00.18362.1316 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.18362.0001 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.18362.1316 Video Renderer,0x00400000,1,0,quartz.dll,10.00.18362.1316 MPC Video Renderer,0x00200000,1,0,MpcVideoRenderer64.ax,0.05.0003.1699 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.18362.0001 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.18362.0001 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax, File writer,0x00200000,1,0,qcap.dll,10.00.18362.0001 DirectVobSub,0x00200000,2,1,vsfilter.dll,3.02.0000.0805 DirectVobSub (auto-loading version),0x00800002,2,1,vsfilter.dll,3.02.0000.0805 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.18362.1316 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.18362.1316 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.18362.0001 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.18362.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.18362.0900 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.18362.0001 LAV Splitter Source,0x00400001,0,1,LAVSplitter.ax,0.75.0000.0002 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.18362.1316 Null Renderer,0x00200000,1,0,qedit.dll,10.00.18362.1316 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.18362.0001 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.18362.0001 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.18362.0001 Smart Tee,0x00200000,1,2,qcap.dll,10.00.18362.0001 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.18362.1316 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.18362.1316 Wave Parser,0x00400000,1,1,quartz.dll,10.00.18362.1316 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.18362.1316 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.18362.1316 File stream renderer,0x00400000,1,1,quartz.dll,10.00.18362.1316 madVR,0x00200000,1,0,madVR64.ax,0.92.0017.0000 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.18362.0001 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.18362.0001 AVI Mux,0x00200000,1,0,qcap.dll,10.00.18362.0001 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.18362.1316 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.18362.1316 File Source (URL),0x00400000,0,1,quartz.dll,10.00.18362.1316 LAV Audio Decoder,0x00800801,1,1,LAVAudio.ax,0.75.0000.0002 LAV Video Decoder,0xff800000,1,1,LAVVideo.ax,0.75.0000.0002 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.18362.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.18362.0001 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.18362.0001 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.18362.1316 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.18362.1316 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.18362.1440 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.18362.0001 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.18362.0001 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.18362.0001 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.18362.1316 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.18362.1082 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.18362.1082 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.18362.1316 PCM,0x00200000,1,1,quartz.dll,10.00.18362.1316 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.18362.1316 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.18362.1316 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.18362.1316 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.18362.1316 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.18362.1316 Audio Capture Sources: Microphone (2- Logitech USB Headset),0x00200000,0,0,qcap.dll,10.00.18362.0001 Internal Microphone (Conexant ISST Audio),0x00200000,0,0,qcap.dll,10.00.18362.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.18362.1316 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.18362.1316 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.18362.1316 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.18362.1316 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.18362.1316 WDM Streaming Capture Devices: HP HD Camera,0x00200000,1,2,ksproxy.ax,10.00.18362.1316 Conexant ISST Stereo Mix,0x00200000,1,1,ksproxy.ax,10.00.18362.1316 Conexant ISST Audio capture,0x00200000,1,1,ksproxy.ax,10.00.18362.1316 Logitech USB Headset,0x00200000,2,2,ksproxy.ax,10.00.18362.1316 HP Dock Audio Device,0x00200000,2,2,ksproxy.ax,10.00.18362.1316 WDM Streaming Rendering Devices: Conexant ISST Audio output,0x00200000,2,2,ksproxy.ax,10.00.18362.1316 HP Dock Audio Device,0x00200000,2,2,ksproxy.ax,10.00.18362.1316 Intel(R) Display Audio Output 2.1,0x00200000,1,1,ksproxy.ax,10.00.18362.1316 Intel(R) Display Audio Output 2.2,0x00200000,1,1,ksproxy.ax,10.00.18362.1316 Logitech USB Headset,0x00200000,2,2,ksproxy.ax,10.00.18362.1316 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.18362.0001 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.18362.0001 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.18362.0001 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.18362.0001 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.18362.0001 Video Capture Sources: HP HD Camera,0x00200000,1,2,ksproxy.ax,10.00.18362.1316 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.18362.1316 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.18362.0001 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.18362.0001 BDA CP/CA Filters: Decrypt/Tag,0x00600000,1,1,msvidctl.dll,6.05.18362.1316 Encrypt/Tag,0x00200000,0,0,, PTFilter,0x00200000,0,0,, XDS Codec,0x00200000,0,0,, WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.18362.1316 Audio Renderers: Speakers (2- Logitech USB Headset),0x00200000,1,0,quartz.dll,10.00.18362.1316 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.18362.1316 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.18362.1316 DirectSound: H243H (Intel(R) Display Audio),0x00200000,1,0,quartz.dll,10.00.18362.1316 DirectSound: H243H (Intel(R) Display Audio),0x00200000,1,0,quartz.dll,10.00.18362.1316 DirectSound: Speakers (Conexant ISST Audio),0x00200000,1,0,quartz.dll,10.00.18362.1316 DirectSound: Speakers (2- Logitech USB Headset),0x00200000,1,0,quartz.dll,10.00.18362.1316 H243H (Intel(R) Display Audio),0x00200000,1,0,quartz.dll,10.00.18362.1316 H243H (Intel(R) Display Audio),0x00200000,1,0,quartz.dll,10.00.18362.1316 Speakers (Conexant ISST Audio),0x00200000,1,0,quartz.dll,10.00.18362.1316 ---------------------------- Preferred DirectShow Filters ---------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred] , [, ] {31305641-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {30345652-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {30395056-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {30385056-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {31435648-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {43564548-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {30357864-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {30355844-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {31637661-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} 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}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {7634706D-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_mp4s, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {64697678-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {58564944-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} {5634504D-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_MP4S, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_WMVR, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject {44495658-0000-0010-8000-00AA00389B71}, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_WMVA, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mpg4, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_MPG4, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_h264, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_H264, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_WMV3, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp43, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_MP43, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} 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, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_MP42, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} MEDIASUBTYPE_WMV1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS1, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_WVC1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_AVC1, Enhanced Video Renderer, {FA10746C-9B63-4B6C-BC49-FC300EA5F256} 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, LAV Audio Decoder, {E8E73B6B-4CB3-44A4-BE99-4F7BCB96E491} 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.18362.1500 mfreadwrite.dll, 10.00.18362.1316 mfcaptureengine.dll, 10.00.18362.1316 mfsensorgroup.dll, 10.00.18362.1171 windows.media.dll, 10.00.18362.1350 frameserver.dll, 10.00.18362.1316 fsclient.dll, 10.00.18362.1316 --------------------------- 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, 10.20.0009.0015 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.18362.1500 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.18362.0001 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.18362.1016 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.18362.1500 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.18362.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.18362.1500 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.18362.0900 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.18362.0001 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.18362.0001 WebpImageExtension HEIFImageExtension VP9VideoExtensionDecoder Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 10.20.0009.0015 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 10.20.0009.0015 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.18362.1049 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.18362.1440 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.18362.0001 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.18362.0001 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.18362.0001 HEIFImageExtension VP9VideoExtensionEncoder Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.18362.1316 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.18362.1440 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.18362.1316 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.18362.1316 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.18362.1440 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.18362.1316 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.18362.1443 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.18362.0001 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.18362.1082 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.18362.1377 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.18362.1500 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.18362.1500 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.18362.1082 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.18362.1316 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.18362.1316 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.18362.1377 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.18362.0001 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.18362.1500 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.18362.1500 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.18362.0001 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.18362.1316 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.18362.1500 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.18362.1316 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.18362.1316 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.18362.1316 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.18362.1500 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.18362.1316 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.18362.1082 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.18362.0001 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.18362.0001 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.18362.1082 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.18362.0001 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.18362.1316 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.18362.0001 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.18362.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.18362.0001 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.18362.1440 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.18362.1500 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableVideoProcessors = 1 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 +++: Fault bucket 2107028031971190837, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: wa_3rd_party_host_32.exe P2: 2019.5.28.829 P3: 5ced5944 P4: wa_3rd_party_host_32.exe P5: 2019.5.28.829 P6: 5ced5944 P7: 00099981 P8: c0000409 P9: 00000007 P10: +++ WER1 +++: Fault bucket 2107028031971190837, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: wa_3rd_party_host_32.exe P2: 2019.5.28.829 P3: 5ced5944 P4: wa_3rd_party_host_32.exe P5: 2019.5.28.829 P6: 5ced5944 P7: 00099981 P8: c0000409 P9: 00000007 P10: +++ WER2 +++: Fault bucket 2142802857410691272, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: LogonUI.exe P2: 10.0.18362.1 P3: b2f611fe P4: combase.dll P5: 10.0.18362.1500 P6: f8437249 P7: 8007000e P8: 0000000000085dba P9: P10: +++ WER3 +++: Fault bucket 2277286868341736884, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: PanGpHip.exe P2: 5.0.3.29 P3: 5d1bdc88 P4: MSVCR120.dll P5: 12.0.21005.1 P6: 524f83ff P7: 0000000000074a30 P8: c0000409 P9: 0000000000000007 P10: +++ WER4 +++: Fault bucket 2239244190085131139, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: usocoreworker.exe P2: 10.0.18362.1474 P3: 10.0.18363.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER5 +++: Fault bucket 2303060155610519870, type 5 Event Name: WinSetupDiag02 Response: Not available Cab Id: 0 Problem signature: P1: 6 P2: 1 P3: X P4: 0 P5: 0x0 P6: 0x3001D P7: 18363 P8: 19h1_release P9: X P10: X +++ WER6 +++: Fault bucket 1755354164942946385, type 5 Event Name: UpdateAgentDiag Response: Not available Cab Id: 0 Problem signature: P1: 3 P2: X P3: 5 P4: 0xC1900104 P5: amd64 P6: 18363 P7: 19h1_release P8: 19041 P9: vb_release_svc_prod1 P10: 985 +++ WER7 +++: Fault bucket 2303060155610519870, type 5 Event Name: WinSetupDiag02 Response: Not available Cab Id: 0 Problem signature: P1: 6 P2: 1 P3: X P4: 0 P5: 0x0 P6: 0x3001D P7: 18363 P8: 19h1_release P9: X P10: X +++ WER8 +++: Fault bucket 1755354164942946385, type 5 Event Name: UpdateAgentDiag Response: Not available Cab Id: 0 Problem signature: P1: 3 P2: X P3: 5 P4: 0xC1900104 P5: amd64 P6: 18363 P7: 19h1_release P8: 19041 P9: vb_release_svc_prod1 P10: 985 +++ WER9 +++: Fault bucket 2303060155610519870, type 5 Event Name: WinSetupDiag02 Response: Not available Cab Id: 0 Problem signature: P1: 6 P2: 1 P3: X P4: 0 P5: 0x0 P6: 0x3001D P7: 18363 P8: 19h1_release P9: X P10: X ...#SSU#...