# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"09/09/2020" Time:"00:01:16.8557744" # Scanned Hardware Computer: BaseBoard Manufacturer:"Dell Inc." BIOS Mode:"UEFI" BIOS Version/Date:"Dell Inc. 1.16.2 , 04/21/2020 12:00 AM" CD or DVD:"Not Available" Embedded Controller Version:"255.255" Platform Role:"Mobile" Processor:"Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz , GenuineIntel" Secure Boot State:"On" SMBIOS Version:"3.1" Sound Card:"NVIDIA Virtual Audio Device (Wave Extensible) (WDM)" Sound Card:"Realtek Audio" Sound Card:"USB Audio 2.0" Sound Card:"Intel(R) Display Audio" System Manufacturer:"Dell Inc." System Model:"XPS 15 9570" System SKU:"087C" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"27.20.100.8587" - "DisplayLink USB Device" Adapter Compatibility:"DisplayLink" Adapter DAC Type:"Not Available" Adapter RAM:"Not Available" Availability:"Offline" Bits Per Pixel:"Not Available" Caption:"DisplayLink USB Device" CoInstallers:"oem83.inf,dlidusb3_Install.NT,Not Available,Not Available" Color Table Entries:"Not Available" Dedicated Video Memory:"Not Available" Driver:"WUDFRd.sys" Driver Date:"04/28/2019 09:00 PM" Driver Path:"C:\WINDOWS\system32\drivers\WUDFRd.sys" Driver Provider:"DisplayLink" Driver Version:"9.1.1644.0" INF:"oem83.inf" INF Section:"dlidusb3_Install.NT" Install Date:"Not Available" Installed Drivers:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"003a.0000.0000.003.001.000.000.000.000" Manufacturer:"DisplayLink" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"Not Available" Number of Video Pages:"Not Available" PNP Device ID:"USB\VID_17E9&PID_6006&MI_00\7&11AFD380&0&0000" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"Not Available" Refresh Rate - Maximum:"Not Available" Refresh Rate - Minimum:"Not Available" Resolution:"Not Available" Scan Mode:"Not Available" Service Name:"WUDFRd" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Not Available" - "DisplayLink USB Device" Adapter Compatibility:"DisplayLink" Adapter DAC Type:"Not Available" Adapter RAM:"Not Available" Availability:"Running or Full Power" Bits Per Pixel:"32" Caption:"DisplayLink USB Device" CoInstallers:"oem83.inf,dlidusb3_Install.NT,Not Available,Not Available" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"WUDFRd.sys" Driver Date:"04/28/2019 09:00 PM" Driver Path:"C:\WINDOWS\system32\drivers\WUDFRd.sys" Driver Provider:"DisplayLink" Driver Version:"9.1.1644.0" INF:"oem83.inf" INF Section:"dlidusb3_Install.NT" Install Date:"Not Available" Installed Drivers:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"003a.0000.0000.003.001.000.000.000.000" Manufacturer:"DisplayLink" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"USB\VID_17E9&PID_6006&MI_01\7&11AFD380&0&0001" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"64 Hz" Refresh Rate - Maximum:"64 Hz" Refresh Rate - Minimum:"64 Hz" Resolution:"1920 X 1080" Scan Mode:"Noninterlaced" Service Name:"WUDFRd" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Not Available" - "Intel(R) UHD Graphics 630" Adapter Compatibility:"Intel Corporation" Adapter DAC Type:"Internal" Adapter RAM:"0.00 GB" Availability:"Offline" Bits Per Pixel:"Not Available" - "Caption":"Intel(R) UHD Graphics 630" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=UHD+Graphics+630" CoInstallers:"oem4.inf,iCFL_w10_DS,Internal,Intel(R) UHD Graphics Family" Color Table Entries:"Not Available" Dedicated Video Memory:"Not Available" Driver:"igdkmd64.sys" Driver Date:"08/04/2020 09:00 PM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdkmd64.sys" Driver Provider:"Intel Corporation" Driver Version:"27.20.100.8587" INF:"oem4.inf" INF Section:"iCFL_w10_DS" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\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:"Not Available" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_3E9B&SUBSYS_087C1028&REV_00\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"Not Available" Refresh Rate - Maximum:"Not Available" Refresh Rate - Minimum:"Not Available" Resolution:"Not Available" Scan Mode:"Not Available" Service Name:"igfx" Status:"Error" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) UHD Graphics Family" - "NVIDIA GeForce GTX 1050 Ti with Max-Q Design" Adapter Compatibility:"NVIDIA" Adapter DAC Type:"Integrated RAMDAC" Adapter RAM:"4.00 GB" Availability:"Offline" Bits Per Pixel:"Not Available" Caption:"NVIDIA GeForce GTX 1050 Ti with Max-Q Design" CoInstallers:"oem14.inf,Section101,Integrated RAMDAC,GeForce GTX 1050 Ti with Max-Q Design" Color Table Entries:"Not Available" Dedicated Video Memory:"Not Available" Driver:"nvlddmkm.sys" Driver Date:"08/11/2020 09:00 PM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvlddmkm.sys" Driver Provider:"NVIDIA" Driver Version:"27.21.14.5206" INF:"oem14.inf" INF Section:"Section101" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 1, device 0, function 0" Manufacturer:"NVIDIA" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"Not Available" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_10DE&DEV_1C8C&SUBSYS_087C1028&REV_A1\4&1CFD4D04&0&0008" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"Not Available" Refresh Rate - Maximum:"Not Available" Refresh Rate - Minimum:"Not Available" Resolution:"Not Available" Scan Mode:"Not Available" Service Name:"nvlddmkm" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"GeForce GTX 1050 Ti with Max-Q Design" - "Memory" Physical Memory (Available):"8.06 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.72 GB" - "DIMM A" Capacity:"8 GB" Channel:"DIMM A" Configured Clock Speed:"2667 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"First position" Manufacturer:"80AD000080AD" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"HMA81GS6CJR8N-VK" Serial Number:"721C2901" Status:"Not Available" Type:"Synchronous" - "DIMM B" Capacity:"8 GB" Channel:"DIMM B" Configured Clock Speed:"2667 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Second position" Manufacturer:"80AD000080AD" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"HMA81GS6CJR8N-VK" Serial Number:"721C2971" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"1.16.2, DELL - 1072009" Caption:"Motherboard" - "Chipset":"Intel(R) 300 Series" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=300+Series" Date:"04/20/2020 09:00 PM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"Dell Inc." Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"02MJVY" Serial Number:"/CNJWNQ2/CNCMK00876076D/" Status:"OK" Version:"A00" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Bluetooth Device (Personal Area Network)" Availability:"Running or Full Power" Caption:"Bluetooth Device (Personal Area Network)" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"bthpan.sys" Driver Date:"06/21/2006 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\bthpan.sys" Driver Provider:"Microsoft" Driver Version:"10.0.18362.1" Index:"0003" INF:"bthpan.inf" INF Section:"BthPan.Install" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"09/09/2020 05:49 PM" Location:"Not Available" MAC Address:"3C:6A:A7:1C:2D:EC" Manufacturer:"Microsoft" Media Type: Net Connection ID:"Bluetooth Network Connection" NetCfgInstanceId:"{A66AC93A-DA7D-4EEE-B7D8-8422AF005DD4}" Number of VLANs:"0" PNP Device ID:"BTH\MS_BTHPAN\6&F8F532C&0&2" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Bluetooth Device (Personal Area Network)" Service Name:"BthPan" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Cliente para Redes Microsoft: Compartilhamento Arquivos e Impressoras para Redes Microsoft: Driver de E/S do Mapeador de Descoberta de Topologia de Camada de Link: Driver de Protocolo LLDP da Microsoft: Protocolo IP Versão 4 (TCP/IPv4): Protocolo IP Versão 6 (TCP/IPv6): Respondente de Descoberta de Topologia de Camada de Link: - "Intel(R) Wireless-AC 9260 160MHz" Access Point:"e8:01:8d:49:21:94" Authentication:"WPA2-Personal" Availability:"Running or Full Power" - "Caption":"Intel(R) Wireless-AC 9260 160MHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Wireless+AC+9260+160MHz" Channel:"149" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Profile" Default IP Gateway:"192.168.100.1" DHCP Enabled:"Yes" DHCP Lease Expires:"09/10/2020 05:51 PM" DHCP Lease Obtained:"09/09/2020 05:51 PM" DHCP Server:"192.168.100.1" Driver:"Netwtw08.sys" Driver Date:"05/04/2020 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\Netwtw08.sys" Driver Provider:"Intel" Driver Version:"21.90.3.2" Index:"0001" INF:"oem56.inf" INF Section:"Install_MPCIEX_GENM22_9260_AC_2x2_HMC_WINT_64_AC" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.100.8;fe80::1179:687c:34e3:62e8" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"09/09/2020 05:49 PM" Location:"PCI bus 59, device 0, function 0" MAC Address:"3C:6A:A7:1C:2D:E8" Manufacturer:"Intel Corporation" Media Type: Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{53F4FA3A-4EA2-4C87-8540-3A5A4A51563A}" Network Name:"SuperDinos 5G" Network Type:"Infrastructure" Number of VLANs:"0" PNP Device ID:"PCI\VEN_8086&DEV_2526&SUBSYS_00148086&REV_29\4&115E5835&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) Wireless-AC 9260 160MHz" Profile:"SuperDinos 5G" Radio Type:"802.11ac" Receive Rate:"468 Mbps" Service Name:"Netwtw08" Signal Strength:"90%" State:"connected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate:"866.7 Mbps" Type:"Ethernet 802.3" - "Service Bindings" Agendador de pacotes de serviço: Cliente para Redes Microsoft: Compartilhamento Arquivos e Impressoras para Redes Microsoft: Driver de E/S do Mapeador de Descoberta de Topologia de Camada de Link: Driver de Protocolo LLDP da Microsoft: Protocolo IP Versão 4 (TCP/IPv4): Protocolo IP Versão 6 (TCP/IPv6): Respondente de Descoberta de Topologia de Camada de Link: - "Settings" *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)" *PacketCoalescing:Packet Coalescing:"Enabled (1)" *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)" *PMNSOffload:NS offload for WoWLAN:"Enabled (1)" *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" BgScanGlobalBlocking:Global BG Scan blocking:"Never (0)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"Auto (1)" CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)" FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)" IbssTxPower:Transmit Power:"5. Highest (100)" IEEE11nMode:802.11n/ac Wireless Mode:"3. 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)" - "TAP-Windows Adapter V9" Availability:"Running or Full Power" Caption:"TAP-Windows Adapter V9" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"tap0901.sys" Driver Date:"04/21/2016 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\tap0901.sys" Driver Provider:"TAP-Windows Provider V9" Driver Version:"9.0.0.21" Index:"0013" INF:"oem69.inf" INF Section:"tap0901.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"09/09/2020 05:49 PM" Location:"Not Available" MAC Address:"00:FF:87:49:4D:08" Manufacturer:"TAP-Windows Provider V9" Media Type: Net Connection ID:"Ethernet" NetCfgInstanceId:"{87494D08-6CF6-403F-A161-F27C3CA2F108}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0000" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"TAP-Windows Adapter V9" Service Name:"tap0901" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Agendador de pacotes de serviço: Cliente para Redes Microsoft: Compartilhamento Arquivos e Impressoras para Redes Microsoft: Driver de E/S do Mapeador de Descoberta de Topologia de Camada de Link: Driver de Protocolo LLDP da Microsoft: Protocolo IP Versão 4 (TCP/IPv4): Protocolo IP Versão 6 (TCP/IPv6): Respondente de Descoberta de Topologia de Camada de Link: - "Settings" AllowNonAdmin:Non-Admin Access:"Allowed (1)" MediaStatus:Media Status:"Application Controlled (0)" MTU:MTU:"1500 (1500)" - "Operating System" .Net Framework Version:"4.0,4.8" Boot Device:"\Device\HarddiskVolume1" Internet Browser:"Google Chrome,85.0, Internet Explorer,11.592" Locale:"Brazil" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Pro" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"2.38 GB" Physical Memory (Available):"8.06 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.72 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.18363 Build 18363" Virtual Memory (Available):"7.60 GB" Virtual Memory (Total):"18.10 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB4516115:"Security Update [11/14/2019]" KB4517245:"Update [11/14/2019]" KB4524569:"Security Update [11/14/2019]" KB4528759:"Security Update [2/5/2020]" KB4528760:"Update [2/5/2020]" KB4561600:"Security Update [9/9/2020]" KB4576484:"Update [9/9/2020]" KB4576751:"Security Update [9/9/2020]" - "Processor" - "Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 158 Stepping 10" - "Chipset Name":"Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i7+8750H+CPU+" CPU Speed:"2.21 GHz" Current Voltage:"8. volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.18362.387" 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:"6 x 384 KB" Level 2 Cache:"6 x 1536 KB" Level 3 Cache:"9 MB" Load:"1%" Manufacturer:"GenuineIntel" Model:"158" Name:"Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz" Number of Cores:"6" Number of Cores Enabled:"6" Number of Logical Processors:"12" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000906EA" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"10" Version:"Not Available" - "Storage" - "ADATA SX8200NP" Capablities:"Random Access, Supports Writing" Caption:"ADATA SX8200NP" Cylinder - Total:"116737" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.18362.1" Error Code:"Device is working properly" Firmware Revision:"SVN163" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"ADATA SX8200NP" Name:"\\.\PHYSICALDRIVE0" Partitions:"5" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_ADATA_SX8200NP\5&21A9571C&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"1875379905" Serial Number:"2I4620064488 _00000001." Size:"894.25 GB" Size – Available:"697.03 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"29767935" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"OS" Serial Number:"C2E93F5E" Size:"881.60 GB" Size – Available:"697.03 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x800F081F: 2020-09 Atualização Cumulativa do Windows 10 Version 1909 para sistemas operacionais baseados em x64 (KB4574727). ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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 cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server DellInc.DellDigitalDelivery_4.0.52.0_x64__htrsf667h5kn2!App.AppX8fcchbt2jr8vt2h452vbkk0wjqvgzjhb.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.Cortana_1.13.0.18362_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXd4tad4d57t4wtdbnnmb8v2xtzym8c1n8.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.OneConnect_5.2006.1691.0_x64__8wekyb3d8bbwe!App.AppXe8pdgw5syxe8pgccbk3mcn5hanwamr0e.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 device Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Goodix fingerprint (location 0000.0014.0000.007.000.000.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The SMP de Espaços de Armazenamento da Microsoft service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The Servidor de Quadros de Câmera do Windows service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The server {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 server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024CE2B: Intel Corporation - Display - 26.20.100.7985. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The TeamViewer 12 service terminated unexpectedly. It has done this 3 time(s). ------------------------------------------------------------------- The TeamViewer 12 service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 2000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The TeamViewer 12 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 2000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Windows Update service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- The TeamViewer 12 service terminated unexpectedly. It has done this 3 time(s). ------------------------------------------------------------------- The TeamViewer 12 service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 2000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The TeamViewer 12 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 2000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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 0x800F081F: 2020-09 Atualização Cumulativa do Windows 10 Version 1909 para sistemas operacionais baseados em x64 (KB4574727). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2020-09 Atualização Cumulativa do Windows 10 Version 1909 para sistemas operacionais baseados em x64 (KB4574727). ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The Intel® SGX AESM service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 3000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The Intel® SGX AESM service terminated with the following error: Unspecified error ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: Ferramenta de Remoção de Software Mal-intencionado do Windows x64 - v5.83 (KB890830). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: Atualização do Windows 10 Version 1909 para sistemas baseados em x64 (KB4516421). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x800F081F: 2020-09 Atualização Cumulativa do Windows 10 Version 1909 para sistemas operacionais baseados em x64 (KB4574727). ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine the computer account to enforce Group Policy settings. This may be transient. Group Policy settings, including computer configuration, will not be enforced for this computer. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- Bootmgr failed to obtain the BitLocker volume master key from the TPM. ------------------------------------------------------------------- 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 device Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Goodix fingerprint (location 0000.0014.0000.007.000.000.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The 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. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service BITS with arguments "Não Disponível" in order to run the server: {4991D34B-80A1-4291-83B6-3328366B9097} ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0xC19001E1: Atualização de recursos para o Windows 10, versão 2004. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} 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 NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024CE2B: Intel Corporation - Display - 26.20.100.7985. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The device Dell Universal Dock D6000 (location 0000.0014.0000.017.001.000.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Dell Universal Dock D6000 (location 0000.0014.0000.017.001.000.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The device DisplayLink USB Device (location 0000.0014.0000.017.001.000.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device DisplayLink USB Device (location 0000.0014.0000.017.001.000.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024CE2B: Intel Corporation - Display - 26.20.100.7985. ------------------------------------------------------------------- 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 Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Serviço do Kaspersky Endpoint Security service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070430: Intel Corporation - Extension - 26.20.100.7985. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80070430: Intel Corporation - Display - 26.20.100.7985. ------------------------------------------------------------------- The Dell Data Vault Processor service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer could not authenticate with \\AZSRVDC01.carpacorp.local, a Windows domain controller for domain CARPACORP, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffffe6892b0e7010, 0xfffff80252ab5b20, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c6500577-9be8-4d4d-b2d6-972fb35edbf4. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- The previous system shutdown at 9:54:35 AM on ‎8/‎18/‎2020 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024CE2B: Intel Corporation - Display - 26.20.100.7985. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Otimização de Entrega 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. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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 Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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 Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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 cplspcon service terminated with the following error: Unspecified error ------------------------------------------------------------------- The device Dell Universal Dock D6000 (location 0000.0014.0000.018.001.000.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Dell Universal Dock D6000 (location 0000.0014.0000.018.001.000.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 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:45:30 PM on ‎9/‎8/‎2020 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Não Disponível" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024001E: 2020-06 Atualização de segurança do Adobe Flash Player para Windows 10 Version 1909 para sistemas baseados em x64 (KB4561600). ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Não Disponível" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8007001F: Ferramenta de Remoção de Software Mal-intencionado do Windows x64 - v5.82 (KB890830). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8007001F: Atualização do Windows 10 Version 1909 para sistemas baseados em x64 (KB4516421). ------------------------------------------------------------------- The server {BE19F061-C08B-426E-811F-2A1CEB1E80AD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 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:33:36 PM on ‎9/‎8/‎2020 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 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:15:22 PM on ‎9/‎8/‎2020 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.WindowsStore_12008.1001.1.0_x64__8wekyb3d8bbwe!App.AppX65azfy60a5wn91mcvdd3dr2y0wj02n39.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.WindowsFeedbackHub_1.1907.3152.0_x64__8wekyb3d8bbwe!App.AppXsdjy3vfbpyyren487rr1k4k8g5t1k844.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server microsoft.windowscommunicationsapps_16005.13110.41006.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.18362.449_neutral_neutral_cw5n1h2txyewy!App.AppXw3qcpc7p849541dp39vvqd01bn7z9ybh.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server AD2F1837.HPPrinterControl_115.1.152.0_x64__v10z8vjag6ke6!AD2F1837.HPPrinterControl.AppXvfte7t3xdx0ch134sw5a5v16mgycvehx.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.OneConnect_5.2006.1691.0_x64__8wekyb3d8bbwe!App.AppXe8pdgw5syxe8pgccbk3mcn5hanwamr0e.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server DellInc.DellDigitalDelivery_4.0.52.0_x64__htrsf667h5kn2!App.AppX8fcchbt2jr8vt2h452vbkk0wjqvgzjhb.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- The previous system shutdown at 7:22:57 PM on ‎9/‎5/‎2020 was unexpected. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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 CARPACORP 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 server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 11:18:05 AM on ‎9/‎4/‎2020 was unexpected. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The Dell Data Vault Processor service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Otimização de Entrega service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- 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 server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, 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 Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 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:35:25 PM on ‎8/‎28/‎2020 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- The previous system shutdown at 10:25:26 AM on ‎8/‎21/‎2020 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the CDPSvc service. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, 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 server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Otimização de Entrega service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Otimização de Entrega service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.63.76.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The previous system shutdown at 4:01:53 PM on ‎8/‎7/‎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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the CDPSvc service. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the CDPSvc service. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the CDPSvc service. ------------------------------------------------------------------- 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 server {776DBC8D-7347-478C-8D71-791E12EF49D8} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {776DBC8D-7347-478C-8D71-791E12EF49D8} 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, 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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 Otimização de Entrega service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The Otimização de Entrega service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Publicação de Recursos de Descoberta de Função service terminated with the following error: The requested address is not valid in its context. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 3:50:17 PM on ‎7/‎24/‎2020 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 CARPACORP 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 Publicação de Recursos de Descoberta de Função service terminated with the following error: The requested address is not valid in its context. ------------------------------------------------------------------- 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 {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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- 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 CARPACORP 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Spooler de Impressão service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the CDPSvc service. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 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:27:37 PM on ‎7/‎9/‎2020 was unexpected. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 CARPACORP 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 Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Intel(R) Wireless-AC 9260 : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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. ------------------------------------------------------------------- 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca 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 CARPACORP 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 server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- The previous system shutdown at 9:23:41 AM on ‎7/‎1/‎2020 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c!App.AppXtwmqn4em5r5dpafgj4t4yyxgjfe0hr50.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The session setup to the Windows Domain Controller \\SPSRVDC02.carpacorp.local for the domain CARPACORP is not responsive. The current RPC call from Netlogon on \\NTRJ-CELSO to \\SPSRVDC02.carpacorp.local has been cancelled. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The session setup to the Windows Domain Controller \\SPSRVDC02.carpacorp.local for the domain CARPACORP is not responsive. The current RPC call from Netlogon on \\NTRJ-CELSO to \\SPSRVDC02.carpacorp.local has been cancelled. ------------------------------------------------------------------- The session setup to the Windows Domain Controller \\RJSRVDC03.carpacorp.local for the domain CARPACORP is not responsive. The current RPC call from Netlogon on \\NTRJ-CELSO to \\RJSRVDC03.carpacorp.local has been cancelled. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- 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 CARPACORP 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. ------------------------------------------------------------------- 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 CARPACORP 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 CARPACORP 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 CARPACORP 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. ------------------------------------------------------------------- Intel(R) Wireless-AC 9260 : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- 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 CARPACORP 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 CARPACORP 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 CARPACORP 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 server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} 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. ------------------------------------------------------------------- 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 CARPACORP 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, 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 CARPACORP 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 CARPACORP 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. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the CDPSvc service. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 CARPACORP 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. ------------------------------------------------------------------- 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 CARPACORP 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. ------------------------------------------------------------------- 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 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. ------------------------------------------------------------------- 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 CARPACORP 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 CARPACORP 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 Kaspersky Status Send Service service terminated with the following error: System call failed. ------------------------------------------------------------------- Logon script failed. GPO Name : Default Domain Policy GPO File System Path : \\carpacorp.local\sysvol\carpacorp.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User Script Name: \\localhost\NETLOGON\time.vbs ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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 device Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Goodix fingerprint (location 0000.0014.0000.007.000.000.000.000.000) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- 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 CARPACORP 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. 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 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 CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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 processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The session setup to the Windows Domain Controller \\RJSRVDC03.carpacorp.local for the domain CARPACORP is not responsive. The current RPC call from Netlogon on \\NTRJ-CELSO to \\RJSRVDC03.carpacorp.local has been cancelled. ------------------------------------------------------------------- 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 device WPD FileSystem Volume Driver (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (60000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR19. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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 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 CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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 processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR13. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR13. ------------------------------------------------------------------- Encrypted volume check: Volume information on D: cannot be read. ------------------------------------------------------------------- The device, \Device\Harddisk1\DR7, has a bad block. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2ede73b9-7c74-45e9-9e82-d1de5090a013}, 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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 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 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The session setup to the Windows Domain Controller \\AZSRVDC01.carpacorp.local for the domain CARPACORP is not responsive. The current RPC call from Netlogon on \\NTRJ-CELSO to \\AZSRVDC01.carpacorp.local has been cancelled. ------------------------------------------------------------------- The Dell Data Vault Processor service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Reiniciar o serviço. ------------------------------------------------------------------- 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The session setup to the Windows Domain Controller \\SPSRVDC02.carpacorp.local for the domain CARPACORP is not responsive. The current RPC call from Netlogon on \\NTRJ-CELSO to \\SPSRVDC02.carpacorp.local has been cancelled. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: The RPC server is unavailable. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is sip.carpapatrimonial.com.br. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is sip.carpapatrimonial.com.br. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is sip.carpapatrimonial.com.br. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is sip.carpapatrimonial.com.br. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is sip.carpapatrimonial.com.br. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is sip.carpapatrimonial.com.br. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is sip.carpapatrimonial.com.br. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- 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 CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} 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 CARPACORP 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 server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} 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 CARPACORP 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP due to the following: We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not 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 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 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 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 server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- This computer was not able to set up a secure session with a domain controller in domain CARPACORP 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. ------------------------------------------------------------------- Intel(R) Wireless-AC 9260 : The network adapter has returned an invalid value to the driver. ------------------------------------------------------------------- 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 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 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 CARPACORP 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 driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR3. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- ------------------ System Information ------------------ Time of this report: 9/9/2020, 18:29:38 Machine name: Machine Id: {6C048798-55DF-4E7F-967A-66E5E2C05E7A} Operating System: Windows 10 Pro 64-bit (10.0, Build 18363) (18362.19h1_release.190318-1202) Language: English (Regional Setting: English) System Manufacturer: Dell Inc. System Model: XPS 15 9570 BIOS: 1.16.2 (type: UEFI) Processor: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 CPUs), ~2.2GHz Memory: 16384MB RAM Available OS Memory: 16098MB RAM Page File: 10755MB used, 7774MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 144 DPI (150 percent) System DPI Setting: 144 DPI (150 percent) DWM DPI Scaling: UnKnown Miracast: Not Available Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.1.5 DxDiag Version: 10.00.18362.0387 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: There is a problem with Intel(R) UHD Graphics 630 device. For more information, search for 'graphics device driver error code 43' Display Tab 2: No problems found. Display Tab 3: No problems found. Sound Tab 1: No problems found. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: Microsoft Basic Display Driver Manufacturer: Intel Corporation Chip type: Intel(R) UHD Graphics Family DAC type: Internal Device Type: Display-Only Device Device Key: Enum\PCI\VEN_8086&DEV_3E9B&SUBSYS_087C1028&REV_00 Device Status: 01802400 [DN_HAS_PROBLEM|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: 0000002B [CM_PROB_FAILED_POST_START] Driver Problem Code: Unknown Display Memory: 8048 MB Dedicated Memory: 0 MB Shared Memory: 8048 MB Current Mode: 1920 x 1080 (32 bit) (64Hz) HDR Support: Not Supported Display Topology: Internal Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.639648,0.330078), Green(0.299805,0.599609), Blue(0.149414,0.059570), White Point(0.312500,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: unknown Monitor Id: SHP149A Native Mode: 1920 x 1080(p) (59.999Hz) Output Type: Other Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd12umd64.dll Driver File Version: 27.20.0100.8587 (English) Driver Version: 27.20.100.8587 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 1.3 Graphics Preemption: DMA Compute Preemption: DMA Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Not Supported Power P-states: Not Supported Virtualization: Not Supported Block List: No Blocks Catalog Attributes: N/A Driver Attributes: Final Retail Driver Date/Size: 8/4/2020 9:00:00 PM, 1432696 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B71AF4-43CC-11CF-D462-BA67AFC2C735} Vendor ID: 0x1414 Device ID: 0x008C SubSys ID: 0x00000000 Revision ID: 0x0000 Driver Strong Name: oem4.inf:5f63e53429d61c21:iCFL_w10_DS:27.20.100.8587:PCI\VEN_8086&DEV_3E9B Rank Of Driver: 00CF2001 Video Accel: DXVA2 Modes: Unknown Deinterlace Caps: {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Not Supported DXVA-HD: Not 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: NVIDIA GeForce GTX 1050 Ti with Max-Q Design Manufacturer: NVIDIA Chip type: GeForce GTX 1050 Ti with Max-Q Design DAC type: Integrated RAMDAC Device Type: Render-Only Device Device Key: Enum\PCI\VEN_10DE&DEV_1C8C&SUBSYS_087C1028&REV_A1 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 12069 MB Dedicated Memory: 4021 MB Shared Memory: 8048 MB Current Mode: Unknown HDR Support: Unknown Display Topology: Unknown Display Color Space: Unknown Color Primaries: Unknown Display Luminance: Unknown Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll Driver File Version: 27.21.0014.5206 (English) Driver Version: 27.21.14.5206 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.6 Graphics Preemption: Pixel Compute Preemption: Dispatch Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Discrete Power P-states: Not Supported Virtualization: Paravirtualization Block List: No Blocks Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 8/11/2020 9:00:00 PM, 1038352 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: Unknown Vendor ID: 0x10DE Device ID: 0x1C8C SubSys ID: 0x087C1028 Revision ID: 0x00A1 Driver Strong Name: oem14.inf:0f066de32a171abf:Section101:27.21.14.5206:pci\ven_10de&dev_1c8c&subsys_087c1028 Rank Of Driver: 00CF0001 Video Accel: Unknown DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 Deinterlace Caps: n/a D3D9 Overlay: Unknown DXVA-HD: Unknown DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 0 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: DisplayLink USB Device Manufacturer: DisplayLink Chip type: Unknown DAC type: Unknown Device Type: Display-Only Device Device Key: Enum\USB\VID_17E9&PID_6006&MI_00 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: 8048 MB Dedicated Memory: 0 MB Shared Memory: 8048 MB Current Mode: Unknown HDR Support: Unknown Display Topology: Unknown Display Color Space: Unknown Color Primaries: Unknown Display Luminance: Unknown Driver Name: c:\windows\system32\drivers\umdf\dlidusb3.dll,c:\windows\system32\drivers\wudfrd.sys Driver File Version: 9.01.1644.0000 (English) Driver Version: 9.1.1644.0 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 1.3 Graphics Preemption: DMA Compute Preemption: DMA Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Not Supported Power P-states: Not Supported Virtualization: Not Supported Block List: No Blocks Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 4/28/2019 9:00:00 PM, 8337520 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: Unknown Vendor ID: 0x1414 Device ID: 0x008C SubSys ID: 0x00000000 Revision ID: 0x0000 Driver Strong Name: oem83.inf:c14ce8840c48fa1f:dlidusb3_Install.NT:9.1.1644.0:USB\VID_17E9&PID_6006&MI_00 Rank Of Driver: 00FF0001 Video Accel: Unknown DXVA2 Modes: Unknown Deinterlace Caps: n/a D3D9 Overlay: Unknown DXVA-HD: Unknown DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 0 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: Fones de ouvido/Alto falantes (Realtek(R) Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0298&SUBSYS_1028087C&REV_1001 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHD64.sys Driver Version: 6.00.8991.0001 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 7/21/2020 12:00:00 AM, 6088288 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. 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 (Realtek(R) Audio) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: RTKVHD64.sys Driver Version: 6.00.8991.0001 (English) Driver Attributes: Final Retail Date and Size: 7/23/2020 01:08:36, 6088288 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 1 --------------------- FriendlyName: Integrated Webcam Category: Camera SymbolicLink: \\?\usb#vid_0c45&pid_671d&mi_00#6&1b808df3&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 Manufacturer: Microsoft HardwareID: USB\VID_0C45&PID_671D&REV_8131&MI_00,USB\VID_0C45&PID_671D&MI_00 DriverDesc: USB Video Device DriverProvider: Microsoft DriverVersion: 10.0.18362.1 DriverDateEnglish: 6/21/2006 00:00:00 DriverDateLocalized: 6/21/2006 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: Integrated Webcam Parent: USB\VID_0C45&PID_671D\5&2486ec97&0&12 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \FileSystem\KLIF,\Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {20C94C5C-F402-4F1F-B324-0C1CF0257870} MFT0: n/a DMFT: n/a CustomCaptureSource: n/a DependentStillCapture: False EnablePlatformDMFT: False DMFTChain: n/a 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: Intel(R) HID Event Filter Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x8087, 0x0A1E FF Driver: n/a Device Name: Converted Portable Device Control device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0000 FF Driver: n/a Device Name: Converted Portable Device Control device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0000 FF Driver: n/a Device Name: Intel(R) HID Event Filter Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x8087, 0x0A1E FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0x7A13 FF Driver: n/a Device Name: D6000 Controller Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06C4, 0xC411 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0x7A13 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0xA36D | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 3/19/2019 01:43:43, 618296 bytes | +-+ USB Input Device | | Vendor/Product ID: 0x413C, 0x301A | | Location: Port_#0001.Hub_#0001 | | Matching Device ID: USB\Class_03&SubClass_01 | | Service: HidUsb | | Driver: hidusb.sys, 11/14/2019 16:25:56, 45568 bytes | | Driver: hidclass.sys, 11/14/2019 16:25:56, 211968 bytes | | Driver: hidparse.sys, 11/14/2019 16:25:56, 46080 bytes | | | +-+ HID-compliant mouse | | | Vendor/Product ID: 0x413C, 0x301A | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | Service: mouhid | | | Driver: mouhid.sys, 3/19/2019 01:43:43, 35840 bytes | | | Driver: mouclass.sys, 3/19/2019 01:43:43, 66872 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + Standard PS/2 Keyboard | Matching Device ID: *PNP0303 | Service: i8042prt | Driver: i8042prt.sys, 3/19/2019 01:43:43, 119296 bytes | Driver: kbdclass.sys, 3/19/2019 01:43:43, 70968 bytes | + HID Keyboard Device | Vendor/Product ID: 0x045E, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 3/19/2019 01:43:43, 46592 bytes | Driver: kbdclass.sys, 3/19/2019 01:43:43, 70968 bytes | + HID-compliant mouse | Vendor/Product ID: 0x06CB, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 3/19/2019 01:43:43, 35840 bytes | Driver: mouclass.sys, 3/19/2019 01:43:43, 66872 bytes | + PS/2 Compatible Mouse | Matching Device ID: *PNP0F13 | Service: i8042prt | Driver: mouclass.sys, 3/19/2019 01:43:43, 66872 bytes | Driver: i8042prt.sys, 3/19/2019 01:43:43, 119296 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 713.8 GB Total Space: 902.8 GB File System: NTFS Model: ADATA SX8200NP -------------- System Devices -------------- Name: Intel(R) PCIe Controller (x16) - 1901 Device ID: PCI\VEN_8086&DEV_1901&SUBSYS_087C1028&REV_07\3&11583659&0&08 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.0418 (English), 11/14/2019 16:25:56, 436536 bytes Name: Intel(R) PCI Express Root Port #5 - A33C Device ID: PCI\VEN_8086&DEV_A33C&SUBSYS_087C1028&REV_F0\3&11583659&0&E4 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.0418 (English), 11/14/2019 16:25:56, 436536 bytes Name: Intel(R) SMBus - A323 Device ID: PCI\VEN_8086&DEV_A323&SUBSYS_087C1028&REV_10\3&11583659&0&FC Driver: n/a Name: PCI Express Upstream Switch Port Device ID: PCI\VEN_8086&DEV_15DA&SUBSYS_087C1028&REV_02\UEE4234A2E7C9A00000 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.0418 (English), 11/14/2019 16:25:56, 436536 bytes Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_A348&SUBSYS_087C1028&REV_10\3&11583659&0&FB Driver: C:\WINDOWS\system32\DRIVERS\IntcAudioBus.sys, 10.23.0000.3349 (English), 7/30/2020 09:01:30, 292936 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.18362.0001 (English), 3/19/2019 01:43:37, 98304 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.18362.0001 (English), 3/19/2019 01:43:37, 390656 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15DA&SUBSYS_087C1028&REV_02\EE4234A2E7C9A00010 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.0418 (English), 11/14/2019 16:25:56, 436536 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15DA&SUBSYS_087C1028&REV_02\EE4234A2E7C9A00008 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.0418 (English), 11/14/2019 16:25:56, 436536 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_15DA&SUBSYS_087C1028&REV_02\EE4234A2E7C9A00000 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.0418 (English), 11/14/2019 16:25:56, 436536 bytes Name: Intel(R) Thermal Subsystem - A379 Device ID: PCI\VEN_8086&DEV_A379&SUBSYS_087C1028&REV_10\3&11583659&0&90 Driver: n/a Name: NVIDIA GeForce GTX 1050 Ti with Max-Q Design Device ID: PCI\VEN_10DE&DEV_1C8C&SUBSYS_087C1028&REV_A1\4&1CFD4D04&0&0008 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\NVDisplay.Container.exe, 1.25.2802.9499 (English), 8/13/2020 20:05:00, 883104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\NvContainerRecovery.bat, 8/12/2020 22:47:15, 1951 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\plugins\LocalSystem\NvXDCore.dll, 27.21.0014.5206 (English), 8/13/2020 20:05:08, 1754528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\plugins\LocalSystem\NvcDispCorePlugin.dll, 27.21.0014.5206 (English), 8/13/2020 20:05:02, 519400 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\plugins\LocalSystem\NvcDispWatchdog.dll, 1.25.2802.9499 (English), 8/13/2020 20:05:04, 628472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\plugins\LocalSystem\_DisplayDriverRAS.dll, 1.10.0000.0000 (English), 8/13/2020 20:05:10, 2571160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\plugins\Session\NvFBCPlugin.dll, 6.14.0014.5206 (English), 8/13/2020 20:05:10, 1337064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\plugins\Session\_nvppo.dll, 27.21.0014.5206 (English), 8/13/2020 20:05:16, 1262824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\plugins\Session\nvprofileupdaterplugin.dll, 27.21.0014.5206 (English), 8/13/2020 20:05:12, 2164112 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\Display.NvContainer\plugins\Session\nvxdsyncplugin.dll, 8.17.0014.5206 (English), 8/13/2020 20:05:14, 1798384 bytes Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\Drs\dbInstaller.exe, 27.21.0014.5206 (English), 8/13/2020 19:58:58, 730016 bytes Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\Drs\nvdrsdb.bin, 8/12/2020 22:47:15, 1694832 bytes Driver: C:\WINDOWS\system32\nvcpl.dll, 8.17.0014.5206 (English), 8/13/2020 19:59:44, 5501328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nv3dappshext.dll, 6.14.0014.5206 (English), 8/13/2020 19:59:16, 999672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nv3dappshextr.dll, 6.14.0014.5206 (Portuguese), 8/13/2020 19:59:16, 93072 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvcoproc.bin, 8/12/2020 22:47:15, 9270477 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvcpl.dll, 8.17.0014.5206 (English), 8/13/2020 19:59:44, 5501328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvdevtools.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:16, 4533992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvdevtoolsr.dll, 27.21.0014.5206 (Portuguese), 8/13/2020 20:00:18, 234384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvdisps.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:22, 11580648 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvdispsr.dll, 27.21.0014.5206 (Portuguese), 8/13/2020 20:00:24, 11144936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvgames.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:52, 12290960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvgamesr.dll, 27.21.0014.5206 (Portuguese), 8/13/2020 20:00:56, 12429040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvlicensings.dll, 6.14.0014.5206 (English), 8/13/2020 20:01:44, 4532456 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvlicensingsr.dll, 6.14.0014.5206 (Portuguese), 8/13/2020 20:01:46, 292752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvshext.dll, 1.02.0000.0001 (English), 8/13/2020 20:03:32, 130960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvsmartmax.dll, 6.14.0010.10003 (English), 8/13/2020 20:03:34, 203680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvsmartmax64.dll, 6.14.0010.10003 (English), 8/13/2020 20:03:36, 243088 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvsmartmaxapp.exe, 6.14.0010.10003 (English), 8/13/2020 20:03:38, 273136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvsmartmaxapp64.exe, 6.14.0010.10003 (English), 8/13/2020 20:03:40, 283896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvsvc64.dll, 27.21.0014.5206 (English), 8/13/2020 20:03:44, 2643360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvsvcr.dll, 27.21.0014.5206 (English), 8/13/2020 20:03:46, 1767656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvsvs.dll, 27.21.0014.5206 (English), 8/13/2020 20:03:48, 5053176 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvsvsr.dll, 27.21.0014.5206 (English), 8/13/2020 20:03:50, 1946360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvui.dll, 8.17.0014.5206 (English), 8/13/2020 20:03:54, 6547704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvuir.dll, 8.17.0014.5206 (Portuguese), 8/13/2020 20:03:58, 2471840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvvitvs.dll, 27.21.0014.5206 (English), 8/13/2020 20:04:06, 7396600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvvitvsr.dll, 27.21.0014.5206 (Portuguese), 8/13/2020 20:04:06, 4112616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvwss.dll, 27.21.0014.5206 (English), 8/13/2020 20:04:20, 12063120 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvwssr.dll, 27.21.0014.5206 (Portuguese), 8/13/2020 20:04:22, 9346448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvxdapix.dll, 8.17.0014.5206 (English), 8/13/2020 20:04:26, 8899472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvxdbat.dll, 8.17.0014.5206 (English), 8/13/2020 20:04:30, 1605352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvxdplcy.dll, 8.17.0014.5206 (English), 8/13/2020 20:04:32, 1855208 bytes Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\license.txt, 8/12/2020 22:47:15, 27216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Adjustments.yaml, 8/12/2020 22:47:15, 8964 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Adjustments.yfx, 8/12/2020 22:47:15, 1271 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\BlacknWhite.yaml, 8/12/2020 22:47:15, 5774 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\BlacknWhite.yfx, 8/12/2020 22:47:15, 1080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Color.yaml, 8/12/2020 22:47:15, 5298 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Color.yfx, 8/12/2020 22:47:15, 1951 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Colorblind.yaml, 8/12/2020 22:47:15, 3853 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Colorblind.yfx, 8/12/2020 22:47:15, 1531 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\DOF.yaml, 8/12/2020 22:47:15, 16008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\DOF.yfx, 8/12/2020 22:47:15, 12413 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Details.yaml, 8/12/2020 22:47:15, 5222 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Details.yfx, 8/12/2020 22:47:15, 4077 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\FreqTransfer32.exe, 8/13/2020 20:05:20, 3706088 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\FreqTransfer64.exe, 8/13/2020 20:05:22, 4051176 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\GreenScreen.yaml, 8/12/2020 22:47:15, 5882 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\GreenScreen.yfx, 8/12/2020 22:47:15, 2034 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\GreenScreenBG01.jpg, 8/12/2020 22:47:15, 281528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\GreenScreenBG02.jpg, 8/12/2020 22:47:15, 499736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\HighresBlender32.exe, 8/13/2020 20:05:24, 3828456 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\HighresBlender64.exe, 8/13/2020 20:05:24, 4187536 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\LDR_RGB1_18.png, 8/12/2020 22:47:15, 3671 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Letterbox.yaml, 8/12/2020 22:47:15, 3295 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Letterbox.yfx, 8/12/2020 22:47:15, 1319 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\NightMode.yaml, 8/12/2020 22:47:15, 1738 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\NightMode.yfx, 8/12/2020 22:47:15, 552 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\NvCamera32.dll, 7.00.0600.0612 (English), 8/13/2020 20:05:26, 6798736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\NvCamera64.dll, 7.00.0600.0612 (English), 8/13/2020 20:05:28, 7885200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\NvCameraEnable.exe, 8/13/2020 20:05:28, 365288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\NvCameraWhitelisting32.dll, 7.00.0600.0612 (English), 8/13/2020 20:05:30, 503528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\NvCameraWhitelisting64.dll, 7.00.0600.0612 (English), 8/13/2020 20:05:32, 635624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\NvImageConvert32.exe, 8/13/2020 20:05:34, 3748072 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\NvImageConvert64.exe, 8/13/2020 20:05:34, 4080360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\OldFilm.yaml, 8/12/2020 22:47:15, 7473 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\OldFilm.yfx, 8/12/2020 22:47:15, 2746 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Posterize.fx, 8/12/2020 22:47:15, 12310 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\ReShadeFXC32.exe, 2.00.0000.0000 (English), 8/13/2020 20:05:36, 719592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\RemoveHud.yaml, 8/12/2020 22:47:15, 459 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\RemoveHud.yfx, 8/12/2020 22:47:15, 776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sharpen.yaml, 8/12/2020 22:47:15, 3030 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sharpen.yfx, 8/12/2020 22:47:15, 4993 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\SpecialFX.yaml, 8/12/2020 22:47:15, 14100 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\SpecialFX.yfx, 8/12/2020 22:47:15, 13357 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\SphericalEquirect32.exe, 8/13/2020 20:05:38, 3702160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\SphericalEquirect64.exe, 8/13/2020 20:05:38, 3984272 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Splitscreen.yaml, 8/12/2020 22:47:15, 9609 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Splitscreen.yfx, 8/12/2020 22:47:15, 7203 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sticker01.png, 8/12/2020 22:47:15, 49695 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sticker02.png, 8/12/2020 22:47:15, 474002 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sticker03.png, 8/12/2020 22:47:15, 380006 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sticker04.png, 8/12/2020 22:47:15, 86881 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sticker05.png, 8/12/2020 22:47:15, 59304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sticker06.png, 8/12/2020 22:47:15, 13547 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sticker07.png, 8/12/2020 22:47:15, 6342 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Sticker08.png, 8/12/2020 22:47:15, 96493 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Stickers.yaml, 8/12/2020 22:47:15, 10323 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Stickers.yfx, 8/12/2020 22:47:15, 3989 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\TiltShift.yaml, 8/12/2020 22:47:15, 4656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\TiltShift.yfx, 8/12/2020 22:47:15, 4849 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Vignette.yaml, 8/12/2020 22:47:15, 4677 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\Vignette.yfx, 8/12/2020 22:47:15, 1823 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\YAMLFXC32.exe, 8/13/2020 20:05:40, 1046760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\d3dcompiler_47_32.dll, 6.03.9600.16384 (English), 8/13/2020 20:05:18, 3467496 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\d3dcompiler_47_64.dll, 6.03.9600.16384 (English), 8/13/2020 20:05:18, 4175760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\filternames.cfg, 8/12/2020 22:47:15, 14012 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\fxtools.cfg, 8/12/2020 22:47:15, 65 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\scratches.jpg, 8/12/2020 22:47:15, 346354 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\tools_licenses.txt, 8/12/2020 22:47:15, 11045 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvCamera\ui.tga, 8/12/2020 22:47:15, 120236 bytes Driver: C:\WINDOWS\system32\MCU.exe, 1.01.5204.20580 (English), 8/13/2020 19:59:12, 849640 bytes Driver: C:\WINDOWS\system32\nvdebugdump.exe, 6.14.0014.5206 (English), 8/13/2020 20:00:10, 443624 bytes Driver: C:\WINDOWS\system32\nvidia-smi.exe, 8.17.0014.5206 (English), 8/13/2020 20:01:08, 582904 bytes Driver: C:\WINDOWS\system32\nvml.dll, 8.17.0014.5206 (English), 8/13/2020 20:01:50, 1018768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvopencl32.dll, 27.21.0014.5206 (English), 8/13/2020 20:02:22, 30264720 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvopencl64.dll, 27.21.0014.5206 (English), 8/13/2020 20:02:30, 35529616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvcompiler32.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:24, 35440032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvcompiler64.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:32, 40572320 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvlddmkm.sys, 27.21.0014.5206 (English), 8/13/2020 20:01:38, 24694504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nv-vk64.json, 8/12/2020 22:47:15, 671 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvDecMFTMjpeg.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:12, 603368 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvDecMFTMjpegx.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:14, 745704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvEncMFTH264.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:34, 1132944 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvEncMFTH264x.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:36, 1443216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvEncMFThevc.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:40, 1139600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvEncMFThevcx.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:42, 1450728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvcbl64.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:18, 671480 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvcuda32.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:46, 17365912 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvcuda64.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:52, 20036328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvd3dumx.dll, 27.21.0014.5206 (English), 8/13/2020 19:58:34, 25092232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvd3dumx_cfg.dll, 27.21.0014.5206 (English), 8/13/2020 19:58:42, 25296728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvdlistx.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:30, 207592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumdx.dll, 27.21.0014.5206 (English), 8/13/2020 19:58:58, 1038352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvoglv64.dll, 27.21.0014.5206 (English), 8/13/2020 20:02:12, 41951136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvoptix.dll, 7.01.0000.0000 (English), 8/13/2020 20:02:44, 123312360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvptxJitCompiler32.dll, 27.21.0014.5206 (English), 8/13/2020 20:03:10, 7095192 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvptxJitCompiler64.dll, 27.21.0014.5206 (English), 8/13/2020 20:03:12, 7979752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvrtum64.dll, 27.21.0014.5206 (English), 8/13/2020 20:03:18, 34744224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvvkwddc64.dll, 8/13/2020 20:04:12, 165280 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvwgf2umx.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:16, 43784216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvwgf2umx_cfg.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:28, 44195768 bytes Driver: C:\WINDOWS\system32\NvFBC64.dll, 6.14.0014.5206 (English), 8/13/2020 20:00:50, 2078096 bytes Driver: C:\WINDOWS\system32\NvIFR64.dll, 6.14.0014.5206 (English), 8/13/2020 20:01:30, 1485544 bytes Driver: C:\WINDOWS\system32\NvIFROpenGL.dll, 27.21.0014.5206 (English), 8/13/2020 20:01:34, 669416 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 2.02.0005.0000 (English), 8/17/2020 14:56:34, 119696 bytes Driver: C:\WINDOWS\system32\nvEncodeAPI64.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:46, 811240 bytes Driver: C:\WINDOWS\system32\nvapi64.dll, 27.21.0014.5206 (English), 8/13/2020 19:58:22, 5395088 bytes Driver: C:\WINDOWS\system32\nvcuda.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:00, 2376080 bytes Driver: C:\WINDOWS\system32\nvcuvid.dll, 7.17.0014.5206 (English), 8/13/2020 20:00:08, 6653328 bytes Driver: C:\WINDOWS\system32\nvinfo.pb, 8/12/2020 22:47:15, 77891 bytes Driver: C:\WINDOWS\system32\nvofapi64.dll, 8/13/2020 20:01:58, 675224 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1049296 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1049296 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1745768 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1745768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nv-vk32.json, 8/12/2020 22:47:15, 671 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvIccAdvancedColorIdentity.icm, 8/12/2020 22:47:15, 3288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvd3dum.dll, 27.21.0014.5206 (English), 8/13/2020 19:58:26, 20901328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvd3dum_cfg.dll, 27.21.0014.5206 (English), 8/13/2020 19:58:50, 21269448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvdispco64.exe, 1.00.0015.0000 (English), 8/13/2020 20:00:20, 1536232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvdlist.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:28, 176528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvldumd.dll, 27.21.0014.5206 (English), 8/13/2020 19:58:56, 861464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvoglv32.dll, 27.21.0014.5206 (English), 8/13/2020 20:02:00, 31255288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvvkwddc32.dll, 8/13/2020 20:04:10, 126200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvwgf2um.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:02, 38601048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\nvwgf2um_cfg.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:42, 39321176 bytes Driver: C:\WINDOWS\SysWow64\NvFBC.dll, 6.14.0014.5206 (English), 8/13/2020 20:00:48, 1570704 bytes Driver: C:\WINDOWS\SysWow64\NvIFR.dll, 6.14.0014.5206 (English), 8/13/2020 20:01:28, 1146256 bytes Driver: C:\WINDOWS\SysWow64\NvIFROpenGL.dll, 27.21.0014.5206 (English), 8/13/2020 20:01:32, 555920 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 2.02.0005.0000 (English), 8/17/2020 14:56:34, 104336 bytes Driver: C:\WINDOWS\SysWow64\nvEncodeAPI.dll, 27.21.0014.5206 (English), 8/13/2020 20:00:44, 656784 bytes Driver: C:\WINDOWS\SysWow64\nvapi.dll, 27.21.0014.5206 (English), 8/13/2020 19:58:20, 4707696 bytes Driver: C:\WINDOWS\SysWow64\nvcuda.dll, 27.21.0014.5206 (English), 8/13/2020 19:59:58, 3916688 bytes Driver: C:\WINDOWS\SysWow64\nvcuvid.dll, 7.17.0014.5206 (English), 8/13/2020 20:00:02, 5882600 bytes Driver: C:\WINDOWS\SysWow64\nvofapi.dll, 8/13/2020 20:01:56, 541928 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 912592 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 912592 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1351520 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1351520 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmi.inf_amd64_c494aee3704c1cad\NvTelemetry64.dll, 14.03.0060.0000 (English), 8/13/2020 20:03:52, 4465048 bytes Name: Intel(R) Serial IO I2C Host Controller - A368 Device ID: PCI\VEN_8086&DEV_A368&SUBSYS_087C1028&REV_10\3&11583659&0&A8 Driver: C:\WINDOWS\system32\DRIVERS\iaLPSS2i_I2C_CNL.sys, 30.100.1816.0003 (English), 3/19/2019 01:43:34, 180736 bytes Name: Intel(R) Management Engine Interface Device ID: PCI\VEN_8086&DEV_A360&SUBSYS_087C1028&REV_10\3&11583659&0&B0 Driver: C:\WINDOWS\system32\DRIVERS\TeeDriverW8x64.sys, 2013.14.0000.1529 (English), 6/28/2020 08:47:06, 279248 bytes Name: Intel(R) Host Bridge/DRAM Registers - 3EC4 Device ID: PCI\VEN_8086&DEV_3EC4&SUBSYS_087C1028&REV_07\3&11583659&0&00 Driver: n/a Name: Realtek PCIE CardReader Device ID: PCI\VEN_10EC&DEV_525A&SUBSYS_087C1028&REV_01\00000001004CE00000 Driver: C:\WINDOWS\system32\DRIVERS\RtsPer.sys, 10.00.16299.21305 (English), 5/10/2018 11:44:20, 865216 bytes Driver: C:\WINDOWS\SysWOW64\RsCRIcon.dll, 1.10.0000.0000 (English), 5/10/2018 11:44:20, 9891328 bytes Name: Intel(R) SPI (flash) Controller - A324 Device ID: PCI\VEN_8086&DEV_A324&SUBSYS_087C1028&REV_10\3&11583659&0&FD Driver: n/a Name: PCI standard RAM Controller Device ID: PCI\VEN_8086&DEV_A36F&SUBSYS_087C1028&REV_10\3&11583659&0&A2 Driver: n/a Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_15DB&SUBSYS_087C1028&REV_02\EE4234A2E7C9A00000 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.18362.0207 (English), 11/14/2019 16:25:56, 531976 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.18362.0207 (English), 11/14/2019 16:25:56, 131960 bytes Name: C240 Series Chipset Family LPC Controller (CM246) - A30E Device ID: PCI\VEN_8086&DEV_A30E&SUBSYS_087C1028&REV_10\3&11583659&0&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.18362.0267 (English), 11/14/2019 16:25:56, 19256 bytes Name: Intel(R) PCI Express Root Port #17 - A340 Device ID: PCI\VEN_8086&DEV_A340&SUBSYS_087C1028&REV_F0\3&11583659&0&D8 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.0418 (English), 11/14/2019 16:25:56, 436536 bytes Name: Intel(R) Serial IO I2C Host Controller - A369 Device ID: PCI\VEN_8086&DEV_A369&SUBSYS_087C1028&REV_10\3&11583659&0&A9 Driver: C:\WINDOWS\system32\DRIVERS\iaLPSS2i_I2C_CNL.sys, 30.100.1816.0003 (English), 3/19/2019 01:43:34, 180736 bytes Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_A36D&SUBSYS_087C1028&REV_10\3&11583659&0&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.18362.0207 (English), 11/14/2019 16:25:56, 531976 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.18362.0207 (English), 11/14/2019 16:25:56, 131960 bytes Name: Intel(R) Wireless-AC 9260 160MHz Device ID: PCI\VEN_8086&DEV_2526&SUBSYS_00148086&REV_29\4&115E5835&0&00E0 Driver: C:\WINDOWS\system32\DRIVERS\Netwtw08.sys, 21.80.0006.0002 (English), 5/14/2020 08:59:00, 8914376 bytes Driver: C:\WINDOWS\system32\DRIVERS\Netwfw08.dat, 5/14/2020 08:59:00, 2607948 bytes Driver: C:\WINDOWS\system32\IntelIHVRouter08.dll, 21.80.0000.0001 (English), 5/14/2020 08:59:00, 1062344 bytes Name: Intel(R) Dynamic Platform and Thermal Framework Processor Participant Device ID: PCI\VEN_8086&DEV_1903&SUBSYS_087C1028&REV_07\3&11583659&0&20 Driver: C:\WINDOWS\system32\DRIVERS\dptf_cpu.sys, 8.04.10501.6067 (English), 2/20/2018 14:10:26, 70568 bytes Name: Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) Gaussian Mixture Model - 1911 Device ID: PCI\VEN_8086&DEV_1911&SUBSYS_087C1028&REV_00\3&11583659&0&40 Driver: n/a Name: Intel(R) UHD Graphics 630 Device ID: PCI\VEN_8086&DEV_3E9B&SUBSYS_087C1028&REV_00\3&11583659&0&10 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdkmd64.sys, 27.20.0100.8587 (English), 8/17/2020 14:55:56, 27210592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iglhxs64.vp, 8/17/2020 14:36:38, 5602 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd10iumd64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:18, 24070160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd11dxva64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:26, 62087144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd12dxva64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:34, 61887000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd12umd64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:38, 22347744 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdgmm64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:54, 2228264 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igfxcmrt64.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:20, 212496 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igfx11cmrt64.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:14, 215640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdumdim64.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:12, 1432696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdail64.dll, 8/17/2020 14:55:54, 193424 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd9dxva64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:44, 61865064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iga64.dll, 8/17/2020 14:56:08, 3335352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igc64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:14, 45082576 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\SPIRVDLL.dll, 8/17/2020 14:56:46, 3273616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\UniversalAdapter64.dll, 8/17/2020 14:58:12, 285400 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\opencl-clang64.dll, 2.00.0008.0000 (English), 8/17/2020 14:58:08, 77848904 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdfcl64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:50, 1025760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdmd64.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:00, 10621624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdml64.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:04, 4303496 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdde64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:46, 407432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdinfo64.dll, 8/17/2020 14:56:56, 153696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdext64.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:50, 441216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd10iumd32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:16, 19915024 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd11dxva32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:24, 60794264 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd12dxva32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:30, 60617736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd12umd32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:36, 22130864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdgmm32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:52, 1822296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdumdim32.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:08, 1271024 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdail32.dll, 8/17/2020 14:55:52, 161168 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igd9dxva32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:40, 60583736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igfxcmrt32.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:18, 171256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igfx11cmrt32.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:14, 173376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iga32.dll, 8/17/2020 14:56:06, 2824080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igc32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:12, 39883408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\SPIRVDLL32.dll, 8/17/2020 14:56:48, 2511760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\UniversalAdapter32.dll, 8/17/2020 14:58:10, 243568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\opencl-clang32.dll, 2.00.0008.0000 (English), 8/17/2020 14:58:02, 58402048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdfcl32.dll, 27.20.0100.8587 (English), 8/17/2020 14:55:56, 962960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdmd32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:58, 8675984 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdml32.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:02, 3367016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdde32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:46, 334896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdinfo32.dll, 8/17/2020 14:56:56, 132128 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdext32.dll, 27.20.0100.8587 (English), 8/17/2020 14:56:48, 340528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iglhxo64.vp, 8/17/2020 14:36:38, 42513 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iglhxc64.vp, 8/17/2020 14:36:38, 44194 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iglhxg64.vp, 8/17/2020 14:36:38, 43760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iglhxo64_dev.vp, 8/17/2020 14:36:38, 43143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iglhxc64_dev.vp, 8/17/2020 14:36:38, 43214 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iglhxg64_dev.vp, 8/17/2020 14:36:38, 43732 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iglhxa64.vp, 8/17/2020 14:36:38, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\iglhxa64.cpa, 8/17/2020 14:36:38, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\IntelCpHDCPSvc.exe, 25.20.0100.8587 (English), 8/17/2020 14:56:28, 518000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\cp_resources.bin, 8/17/2020 14:36:30, 2415596 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\ig9icd64.dll, 27.20.0100.8587 (English), 8/17/2020 14:55:52, 16084880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\ig9icd32.dll, 27.20.0100.8587 (English), 8/17/2020 14:55:50, 12932496 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\OSSCOPYRIGHT, 8/17/2020 14:36:44, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igvk64.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:26, 12445680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igvk64.json, 8/17/2020 14:36:38, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\VulkanRT-EULA.txt, 8/17/2020 14:36:46, 4006 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igvk32.dll, 27.20.0100.8587 (English), 8/17/2020 14:57:24, 11026296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igvk32.json, 8/17/2020 14:36:38, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\vulkan-1-64.dll, 1.02.0135.0000 (English), 8/17/2020 14:56:48, 1049296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\vulkaninfo-64.exe, 1.02.0135.0000 (English), 8/17/2020 14:56:50, 1745768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\vulkan-1-32.dll, 1.02.0135.0000 (English), 8/17/2020 14:56:48, 912592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\vulkaninfo-32.exe, 1.02.0135.0000 (English), 8/17/2020 14:56:50, 1351520 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 912592 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1351520 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 912592 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1351520 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1049296 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1745768 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1049296 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.02.0135.0000 (English), 9/9/2020 15:32:32, 1745768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\Intel_OpenCL_ICD32.dll, 2.02.0005.0000 (English), 8/17/2020 14:56:34, 104336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdrcl32.dll, 23.20.0100.8587 (English), 8/17/2020 14:56:00, 4184464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\Intel_OpenCL_ICD64.dll, 2.02.0005.0000 (English), 8/17/2020 14:56:34, 119696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\ze_loader.dll, 8/17/2020 14:56:54, 447376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\ze_validation_layer.dll, 8/17/2020 14:56:54, 136592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\igdrcl64.dll, 23.20.0100.8587 (English), 8/17/2020 14:56:02, 4784032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\ze_intel_gpu64.dll, 8/17/2020 14:56:52, 3988384 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 2.02.0005.0000 (English), 8/17/2020 14:56:34, 104336 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 2.02.0005.0000 (English), 8/17/2020 14:56:34, 119696 bytes Driver: C:\WINDOWS\system32\ze_loader.dll, 8/17/2020 14:56:54, 447376 bytes Driver: C:\WINDOWS\system32\ze_validation_layer.dll, 8/17/2020 14:56:54, 136592 bytes Driver: C:\WINDOWS\SysWow64\libmfxhw32.dll, 8/17/2020 14:57:36, 243712 bytes Driver: C:\WINDOWS\SysWow64\mfxplugin32_hw.dll, 1.20.0007.0007 (English), 8/17/2020 14:56:36, 13505424 bytes Driver: C:\WINDOWS\system32\libmfxhw64.dll, 8/17/2020 14:57:38, 294752 bytes Driver: C:\WINDOWS\system32\mfxplugin64_hw.dll, 1.20.0007.0007 (English), 8/17/2020 14:56:38, 26661776 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:26, 161384 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:28, 136880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\libmfxhw64.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:34, 24397816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfxplugin64_hw.dll, 1.20.0007.0007 (English), 8/17/2020 14:56:38, 26661776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\intel_gfx_api-x64.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:26, 161384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\libmfxhw32.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:30, 23048408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfxplugin32_hw.dll, 1.20.0007.0007 (English), 8/17/2020 14:56:36, 13505424 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\intel_gfx_api-x86.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:28, 136880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_h264ve_32.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:46, 2594384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_mjpgvd_32.dll, 10.20.0007.0007 (English), 8/17/2020 14:56:38, 2454416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_h265ve_32.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:50, 2607400 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_vp9ve_32.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:58, 2601696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_encrypt_32.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:40, 2436008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\c_32.cpa, 8/17/2020 14:36:30, 1361159 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\cpa_32.vp, 8/17/2020 14:36:30, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\dev_32.vp, 8/17/2020 14:36:30, 57143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\he_32.vp, 8/17/2020 14:36:32, 71553 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mj_32.vp, 8/17/2020 14:36:44, 66901 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\h265e_32.vp, 8/17/2020 14:36:30, 73141 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\vp9e_32.vp, 8/17/2020 14:36:46, 72716 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_h264ve_64.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:48, 3203432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_mjpgvd_64.dll, 10.20.0007.0007 (English), 8/17/2020 14:56:40, 3035536 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_h265ve_64.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:56, 3224856 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_vp9ve_64.dll, 10.20.0007.0007 (English), 8/17/2020 14:58:00, 3217552 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mfx_mft_encrypt_64.dll, 10.20.0007.0007 (English), 8/17/2020 14:57:42, 3000808 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\c_64.cpa, 8/17/2020 14:36:30, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\cpa_64.vp, 8/17/2020 14:36:30, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\dev_64.vp, 8/17/2020 14:36:30, 56359 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\he_64.vp, 8/17/2020 14:36:32, 13661 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\mj_64.vp, 8/17/2020 14:36:44, 13393 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\h265e_64.vp, 8/17/2020 14:36:30, 14249 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\vp9e_64.vp, 8/17/2020 14:36:46, 14096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9d53c3023a3ba6b6\IntelCpHeciSvc.exe, 9.02.0004.0820 (English), 8/17/2020 14:56:30, 511856 bytes Name: Intel(R) 300 Series Chipset Family SATA AHCI Controller Device ID: PCI\VEN_8086&DEV_A353&SUBSYS_087C1028&REV_10\3&11583659&0&B8 Driver: C:\WINDOWS\system32\DRIVERS\iaStorAC.sys, 17.08.0000.1065 (English), 12/11/2019 15:54:40, 1339360 bytes Driver: C:\WINDOWS\system32\DRIVERS\RstMwService.exe, 17.08.0000.1065 (English), 12/11/2019 15:54:44, 2241536 bytes Driver: C:\WINDOWS\system32\DRIVERS\RstMwEventLogMsg.dll, 17.08.0000.1065 (English), 12/11/2019 15:54:44, 27104 bytes Name: Standard NVM Express Controller Device ID: PCI\VEN_126F&DEV_2262&SUBSYS_2262126F&REV_03\4&E4C05C&0&00E8 Driver: C:\WINDOWS\system32\DRIVERS\stornvme.sys, 10.00.18362.0001 (English), 3/19/2019 01:43:41, 142648 bytes Name: Intel(R) PCI Express Root Port #1 - A338 Device ID: PCI\VEN_8086&DEV_A338&SUBSYS_087C1028&REV_F0\3&11583659&0&E0 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.0418 (English), 11/14/2019 16:25:56, 436536 bytes Name: Intel(R) PCI Express Root Port #9 - A330 Device ID: PCI\VEN_8086&DEV_A330&SUBSYS_087C1028&REV_F0\3&11583659&0&E8 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.18362.0418 (English), 11/14/2019 16:25:56, 436536 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.18362.0145 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.18362.0145 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.0001 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.18362.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.18362.0001 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.0001 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.18362.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.18362.0001 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.18362.0001 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.18362.0001 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.18362.0592 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.18362.0001 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.18362.0001 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.18362.0001 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.18362.0001 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.18362.0001 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.18362.0001 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.18362.0001 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.0001 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.18362.0001 DV Splitter,0x00600000,1,2,qdv.dll,10.00.18362.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.18362.0001 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.18362.0001 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.18362.0001 Video Renderer,0x00800001,1,0,quartz.dll,10.00.18362.0001 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.0001 Video Renderer,0x00400000,1,0,quartz.dll,10.00.18362.0001 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 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.18362.0001 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.18362.0001 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.0001 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.18362.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.18362.0001 Null Renderer,0x00200000,1,0,qedit.dll,10.00.18362.0001 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.0001 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.18362.0001 Wave Parser,0x00400000,1,1,quartz.dll,10.00.18362.0001 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.18362.0001 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.18362.0001 File stream renderer,0x00400000,1,1,quartz.dll,10.00.18362.0001 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.0001 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.18362.0001 File Source (URL),0x00400000,0,1,quartz.dll,10.00.18362.0001 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.0001 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.18362.0001 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.18362.0001 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.0001 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.18362.0145 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.18362.0145 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.18362.0001 PCM,0x00200000,1,1,quartz.dll,10.00.18362.0001 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.18362.0001 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.18362.0001 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.18362.0001 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.18362.0001 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.18362.0001 Audio Capture Sources: Microphone (Realtek(R) Audio),0x00200000,0,0,qcap.dll,10.00.18362.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.18362.0418 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.18362.0418 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.18362.0418 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.18362.0001 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.18362.0001 WDM Streaming Capture Devices: ,0x00000000,0,0,, Realtek HD Audio Mic input with SST,0x00200000,1,3,ksproxy.ax,10.00.18362.0001 Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.18362.0001 Dell USB Audio,0x00200000,2,2,ksproxy.ax,10.00.18362.0001 Integrated Webcam,0x00200000,1,1,ksproxy.ax,10.00.18362.0001 WDM Streaming Rendering Devices: Realtek HD Audio output with SST,0x00200000,2,2,ksproxy.ax,10.00.18362.0001 Dell USB Audio,0x00200000,2,2,ksproxy.ax,10.00.18362.0001 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: Integrated Webcam,0x00200000,1,1,ksproxy.ax,10.00.18362.0001 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.18362.0001 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 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.18362.0001 Audio Renderers: Fones de ouvido/Alto falantes (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.18362.0001 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.18362.0001 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.18362.0001 DirectSound: Fones de ouvido/Alto falantes (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.18362.0001 ---------------------------- Preferred DirectShow Filters ---------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred] , [, ] MEDIASUBTYPE_DVD_LPCM_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_VIDEO, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS {78766964-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_mp4s, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {64697678-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {58564944-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {5634504D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_MP4S, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject {44495658-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVA, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mpg4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_h264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_H264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_WMV3, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_MP43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMV2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS2, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_M4S2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WVP2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_WMV1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS1, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_WVC1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_AVC1, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_MPEG_LOAS, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG_ADTS_AAC, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_WMAUDIO_LOSSLESS, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_WMAUDIO3, WMAudio Decoder DMO, CLSID_CWMADecMediaObject WMMEDIASUBTYPE_WMAudioV8, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS WMMEDIASUBTYPE_MP3, MP3 Decoder DMO, CLSID_CMP3DecMediaObject MEDIASUBTYPE_MPEG1Payload, MPEG Video Decoder, CLSID_CMpegVideoCodec MEDIASUBTYPE_MPEG1Packet, MPEG Video Decoder, CLSID_CMpegVideoCodec {6C737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64687664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MJPG, MJPEG Decompressor, CLSID_MjpegDec {20637664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MPEG1AudioPayload, MPEG Audio Decoder, CLSID_CMpegAudioCodec WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject WMMEDIASUBTYPE_WMSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject --------------------------- Media Foundation File Versions --------------------------- mfcore.dll, 10.00.18362.0535 mfreadwrite.dll, 10.00.18362.0001 mfcaptureengine.dll, 10.00.18362.0001 mfsensorgroup.dll, 10.00.18362.0207 windows.media.dll, 10.00.18362.0145 frameserver.dll, 10.00.18362.0207 fsclient.dll, 10.00.18362.0207 --------------------------- 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.0007.0007 NVIDIA MJPEG Video Decoder MFT, {70F36578-2741-454F-B494-E8563DDD1CB4}, 0x4, 8, nvDecMFTMjpegx.dll, 27.21.0014.5206 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.18362.0592 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.0001 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.18362.0592 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.18362.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.18362.0001 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.18362.0001 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 VP9VideoExtensionDecoder HEIFImageExtension Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 10.20.0007.0007 NVIDIA H.264 Encoder MFT, {60F44560-5A20-4857-BFEF-D29773CB8040}, 0x4, 8, nvEncMFTH264x.dll, 27.21.0014.5206 NVIDIA HEVC Encoder MFT, {966F107C-8EA2-425D-B822-E4A71BEF01D7}, 0x4, 8, nvEncMFThevcx.dll, 27.21.0014.5206 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 10.20.0007.0007 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.18362.0001 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.18362.0001 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 VP9VideoExtensionEncoder HEIFImageExtension Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.18362.0001 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.18362.0001 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.18362.0001 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.18362.0001 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.18362.0001 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.18362.0387 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.18362.0592 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.0145 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.18362.0175 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.18362.0535 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.18362.0535 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.18362.0145 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.18362.0001 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.18362.0001 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.18362.0175 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.0535 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.18362.0535 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.0001 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.18362.0535 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.18362.0001 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.18362.0001 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.18362.0001 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.18362.0535 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.18362.0001 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.18362.0145 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.0145 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.0001 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.0592 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.18362.0592 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableDecoders = 1 EnableEncoders = 1 ------------------------------------- Media Foundation Byte Stream Handlers ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] .3g2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .ac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .adt, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .am?, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler .amr, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler, Preferred .asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred .dvr-ms, {A8721937-E2FB-4D7A-A9EE-4EB08C890B6E}, MF SBE Source ByteStreamHandler .dvr-ms, {65964407-A5D8-4060-85B0-1CCD63F768E2}, dvr-ms Byte Stream Handler, Preferred .ec3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred .m2t, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m2ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mk3d, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mka, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mks, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mkv, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mov, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp2v, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mpg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .nsc, {B084785C-DDE0-4D30-8CA8-05A373E185BE}, NSC Byte Stream Handler, Preferred .sami, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .smi, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .tod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .uvu, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .vob, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred .weba, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wtv, {65964407-A5D8-4060-85B0-1CCD63F768E2}, WTV Byte Stream Handler, Preferred audio/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/aacp, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/eac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/L16, {3FFB3B8C-EB99-472B-8902-E1C1B05F07CF}, LPCM Byte Stream Handler, Preferred audio/mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/MP4A-LATM, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/vnd.dlna.adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/vnd.dolby.dd-raw, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred audio/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred audio/x-aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/x-flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/x-m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred audio/x-mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-ms-wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred audio/x-wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred video/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/vnd.dece.mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/vnd.dlna.mpeg-tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred video/x-m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred video/x-ms-asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred -------------------------------- Media Foundation Scheme Handlers -------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] file:, {477EC299-1421-4BDD-971F-7CCB933F21AD}, File Scheme Handler, Preferred http:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler http:, {9EC4B4F9-3029-45AD-947B-344DE2A249E2}, Urlmon Scheme Handler http:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpd:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler, Preferred https:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpsd:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcast:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcrecv:, {FA6D33D4-9405-4BA5-9983-12604AC8E77A}, Miracast Sink Scheme Handler, Preferred mms:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ms-appdata:, {CFC81939-3886-4ACF-9692-DA58037AE716}, MsAppData Scheme Handler, Preferred ms-appx-web:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppxWeb Scheme Handler, Preferred ms-appx:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppx Scheme Handler, Preferred ms-winsoundevent:, {F79A6BF9-7415-4CF3-AE10-4559509ABC3C}, Sound Event Scheme Handler, Preferred rtsp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtsps:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred sdp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ------------------------------------- Preferred Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\Preferred] , [, ] {EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B} {E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {A61AC364-AD0E-4744-89FF-213CE0DF8804}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {63616C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905} MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9} {00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} {0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A} {00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} {00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_ADTS, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B} {00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC} {00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE} KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514} {00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786} KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD} WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject ------------------------------------- Disabled Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\DoNotUse] ------------------------ Disabled Media Sources ------------------------ [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse] --------------- EVR Power Information --------------- Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0 --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: Fault bucket 1579126742151119068, type 5 Event Name: UpdateAgentDiag Response: N�o dispon�vel Cab Id: 0 Problem signature: P1: 4 P2: X P3: 5 P4: 0x800F081F P5: amd64 P6: 18363 P7: 19h1_release P8: 18362 P9: 19h1_release_svc_prod1 P10: 1082 +++ WER1 +++: Fault bucket 2246491567703768770, type 5 Event Name: CbsPackageServicingFailure2 Response: N�o dispon�vel Cab Id: 0 Problem signature: P1: 10.0.18362.1073 P2: Package_for_RollupFix P3: 18362.1082.1.10 P4: amd64 P5: unknown P6: 800f081f P7: Resolve P8: Absent P9: Installed P10: UpdateAgentLCU +++ WER2 +++: Fault bucket 1505863642661568245, type 5 Event Name: WindowsWcpOtherFailure3 Response: N�o dispon�vel Cab Id: 0 Problem signature: P1: 10.0.18362.1073:1 P2: wcp\componentstore\csd_transact.cpp P3: CCSDirectTransaction::PreStageUnchangedFiles P4: 1618 P5: c000003a P6: 0x28f9628a P7: P8: P9: P10: +++ WER3 +++: Fault bucket , type 0 Event Name: CbsPackageServicingFailure2 Response: N�o dispon�vel Cab Id: 0 Problem signature: P1: 10.0.18362.1073 P2: Package_for_RollupFix P3: 18362.1082.1.10 P4: amd64 P5: unknown P6: 800f081f P7: Resolve P8: Absent P9: Installed P10: UpdateAgentLCU +++ WER4 +++: Fault bucket , type 0 Event Name: CbsPackageServicingFailure2 Response: N�o dispon�vel Cab Id: 0 Problem signature: P1: 10.0.18362.1073 P2: Package_for_RollupFix P3: 18362.1082.1.10 P4: amd64 P5: unknown P6: 800f081f P7: Resolve P8: Absent P9: Installed P10: UpdateAgentLCU +++ WER5 +++: Fault bucket , type 0 Event Name: WindowsWcpOtherFailure3 Response: N�o dispon�vel Cab Id: 0 Problem signature: P1: 10.0.18362.1073:1 P2: wcp\componentstore\csd_transact.cpp P3: CCSDirectTransaction::PreStageUnchangedFiles P4: 1618 P5: c000003a P6: 0x28f9628a P7: P8: P9: P10: +++ WER6 +++: Fault bucket , type 0 Event Name: WindowsWcpOtherFailure3 Response: N�o dispon�vel Cab Id: 0 Problem signature: P1: 10.0.18362.1073:1 P2: wcp\componentstore\csd_transact.cpp P3: CCSDirectTransaction::PreStageUnchangedFiles P4: 1618 P5: c000003a P6: 0x28f9628a P7: P8: P9: P10: +++ WER7 +++: Fault bucket 1794500129695473464, type 5 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: gfxlauncher.exe P2: 1.0.0.0 P3: 5e2ea7f2 P4: GfxLauncher P5: 1.0.0.0 P6: 5e2ea7f2 P7: 25 P8: 28 P9: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB P10: +++ WER8 +++: Fault bucket 1794500129695473464, type 5 Event Name: CLR20r3 Response: Not available Cab Id: 0 Problem signature: P1: gfxlauncher.exe P2: 1.0.0.0 P3: 5e2ea7f2 P4: GfxLauncher P5: 1.0.0.0 P6: 5e2ea7f2 P7: 25 P8: 28 P9: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB P10: +++ WER9 +++: Fault bucket 1787125596464821501, type 5 Event Name: BEX64 Response: N�o dispon�vel Cab Id: 0 Problem signature: P1: DrvInst.exe P2: 10.0.18362.387 P3: fad3fde1 P4: hpbcoins64.dll P5: 1.0.0.1 P6: 4b5f48d5 P7: 0000000000020fb0 P8: c0000417 P9: 0000000000000000 P10: ...#SSU#...