# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"07/01/2019" Time:"00:00:50.8389465" # Scanned Hardware Computer: BaseBoard Manufacturer:"Dell Inc." BIOS Mode:"UEFI" BIOS Version/Date:"Dell Inc. 1.5.0 , 08/27/2018" CD or DVD:"Not Available" Embedded Controller Version:"255.255" Platform Role:"Mobile" Processor:"Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz , GenuineIntel" Secure Boot State:"On" SMBIOS Version:"3.1" Sound Card:"Intel(R) Display Audio" Sound Card:"Realtek Audio" System Manufacturer:"Dell Inc." System Model:"Latitude 5590" System SKU:"0817" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"24.20.100.6170" - "Intel(R) UHD Graphics 620" Adapter Compatibility:"Intel Corporation" Adapter DAC Type:"Internal" Adapter RAM:"1.00 GB" Availability:"Running or Full Power" Bits Per Pixel:"32" - "Caption":"Intel(R) UHD Graphics 620" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=UHD+Graphics+620" CoInstallers:"oem58.inf,iKBLD_w10_DS_DC5,Internal,Intel(R) UHD Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmd64.sys" Driver Date:"06/18/2018 02:00" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdkmd64.sys" Driver Provider:"Intel Corporation" Driver Version:"24.20.100.6170" INF:"oem58.inf" INF Section:"iKBLD_w10_DS_DC5" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd12umd64.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 0, device 2, function 0" Manufacturer:"Intel Corporation" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_5917&SUBSYS_08171028&REV_07\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"59 Hz" Refresh Rate - Maximum:"59 Hz" Refresh Rate - Minimum:"48 Hz" Resolution:"1920 X 1080" Scan Mode:"Noninterlaced" Service Name:"igfx" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) UHD Graphics Family" - "Memory" Physical Memory (Available):"8.25 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.86 GB" - "BANK 0" Capacity:"8 GB" Channel:"DIMM A" Configured Clock Speed:"2400 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"First position" Manufacturer:"01980000802C" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"KMKYF9-MID" Serial Number:"0407664A" Status:"Not Available" Type:"Not Available" - "BANK 2" Capacity:"8 GB" Channel:"DIMM B" Configured Clock Speed:"2400 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Second position" Manufacturer:"01980000802C" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"KMKYF9-MID" Serial Number:"04075E49" Status:"Not Available" Type:"Not Available" - "Motherboard" Availability:"Running or Full Power" BIOS:"1.5.0, DELL - 1072009" Caption:"Motherboard" - "Chipset":"Intel(R)" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=" Date:"08/27/2018 02:00" 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:"0VYDFF" Serial Number:"/71SR4Q2/CNCMK0086J0112/" Status:"OK" Version:"A00" - "Networking" Intel ® Network Connections Install Options:"ANS,DMIX" Intel ® Network Connections Version:"24.0.0.11" Intel ® PROSet/Wireless Software Version:"21.10.1.0" - "Intel(R) Dual Band Wireless-AC 8265" Access Point:"a6:30:d9:a3:5e:05" Authentication:"WPA2-Personal" Availability:"Running or Full Power" - "Caption":"Intel(R) Dual Band Wireless-AC 8265" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Dual+Band+Wireless+AC+8265" Channel:"100" Cipher:"CCMP" CoInstallers:"Netwuw06.dll,ClassCoInstallerEntryPointWU" Connection Mode:"Auto Connect" Default IP Gateway:"192.168.1.1" DHCP Enabled:"Yes" DHCP Lease Expires:"11/19/1932 11:47" DHCP Lease Obtained:"11/18/1932 11:47" DHCP Server:"192.168.1.1" Driver:"Netwtw06.sys" Driver Date:"04/29/2019 12:00" Driver Path:"C:\WINDOWS\system32\drivers\Netwtw06.sys" Driver Provider:"Intel" Driver Version:"20.70.9.1" Index:"0010" INF:"oem85.inf" INF Section:"Install_MPCIEX_DELLM2_8265_AC_2x2_HMC_WINT_64_AC" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.1.117;fe80::b0ef:dffb:9d7c:88d2" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"06/27/2019 12:15" Location:"PCI bus 2, device 0, function 0" MAC Address:"74:70:FD:BC:5E:EE" Manufacturer:"Intel Corporation" Media Type: Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{F279A5A0-5DA5-4264-B741-B117003BF93A}" Network Name:"MiFibra-5E02" Network Type:"Infrastructure" Number of VLANs:"0" PNP Device ID:"PCI\VEN_8086&DEV_24FD&SUBSYS_00508086&REV_78\7470FDFFFFBC5EEE00" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: No" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Dual Band Wireless-AC 8265" Profile:"MiFibra-5E02" Radio Type:"802.11ac" Receive Rate:"702 Mbps" Service Name:"Netwtw06" Signal Strength:"81%" State:"connected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate:"702 Mbps" Type:"Ethernet 802.3" - "Service Bindings" Cliente para redes Microsoft: Controlador de E/S del asignador de detección de topologías de nivel de vínculo: Controlador de protocolo LLDP de Microsoft: Programador de paquetes QoS: Protocolo de Internet versión 4 (TCP/IPv4): Protocolo de Internet versión 6 (TCP/IPv6): Respondedor de detección de topologías de nivel de vínculo: Uso compartido de archivos e impresoras para redes Microsoft: - "Settings" *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)" *PacketCoalescing:Packet Coalescing:"Enabled (1)" *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)" *PMNSOffload:NS offload for WoWLAN:"Enabled (1)" *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"Auto (1)" CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)" FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)" IbssTxPower:Transmit Power:"5. Highest (100)" IEEE11nMode:802.11n/ac Wireless Mode:"802.11ac (2)" MIMOPowerSaveMode:MIMO Power Save Mode:"Auto SMPS (0)" RoamAggressiveness:Roaming Aggressiveness:"3. Medium (2)" RoamingPreferredBandType:Preferred Band:"1. No Preference (0)" ThroughputBoosterEnabled:Throughput Booster:"Disabled (0)" uAPSDSupport:U-APSD support:"Disabled (0)" WirelessMode:802.11a/b/g Wireless Mode:"6. Dual Band 802.11a/b/g (34)" - "Intel(R) Ethernet Connection (4) I219-LM" Availability:"Running or Full Power" - "Caption":"Intel(R) Ethernet Connection (4) I219-LM" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Ethernet+Connection+(4)+I219+LM" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"e1d68x64.sys" Driver Date:"03/27/2019 12:00" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\e1d68x64.inf_amd64_76c39d852a9f3190\e1d68x64.sys" Driver Provider:"Intel" Driver Version:"12.18.9.2" ETrackID:"0x00000000" Index:"0011" INF:"oem75.inf" INF Section:"E15D7.10.0.1" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"06/27/2019 12:15" Location:"PCI bus 0, device 31, function 6" MAC Address:"10:65:30:69:0D:F7" Manufacturer:"Intel" Media Type:"Copper" Net Connection ID:"Ethernet" NetCfgInstanceId:"{87CB329E-76A3-4F22-8C69-F6040BC3A1EC}" Number of VLANs:"0" NVM Version:"0x00000000" Part Number:"FFFFFF-0FF" PNP Device ID:"PCI\VEN_8086&DEV_15D7&SUBSYS_08171028&REV_21\3&11583659&0&FE" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: No" Power Management (Wake On LAN):"Active: Yes, Enable: No" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Ethernet Connection (4) I219-LM" Service Name:"e1dexpress" Status:"Link Down" Team Name:"Not in a team" Temperature:"Not Supported" Type:"Ethernet 802.3" - "Service Bindings" Cliente para redes Microsoft: Controlador de E/S del asignador de detección de topologías de nivel de vínculo: Controlador de protocolo LLDP de Microsoft: Programador de paquetes QoS: Protocolo de Internet versión 4 (TCP/IPv4): Protocolo de Internet versión 6 (TCP/IPv6): Respondedor de detección de topologías de nivel de vínculo: Uso compartido de archivos e impresoras para redes Microsoft: - "Settings" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Packet:"Disabled (1514)" *LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)" *NumRssQueues:Maximum Number of RSS Queues:"1 Queue (1)" *PMARPOffload:Protocol ARP Offload:"Enabled (1)" *PMNSOffload:Protocol NS Offload:"Enabled (1)" *PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enabled (3)" *ReceiveBuffers:Receive Buffers:"256 (256)" *RSS:Receive Side Scaling:"Enabled (1)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *TransmitBuffers:Transmit Buffers:"512 (512)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Disabled (0)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" AdaptiveIFS:Adaptive Inter-Frame Spacing:"Disabled (0)" AutoPowerSaveModeEnabled:Link Speed Battery Saver:"Disabled (0)" ConnectionName:ConnectionName:"Ethernet (Ethernet)" EEELinkAdvertisement:Energy Efficient Ethernet:"On (1)" EnablePME:Enable PME:"Enabled (1)" ITR:Interrupt Moderation Rate:"Adaptive (65535)" LinkNegotiationProcess:Legacy Switch Compatibility Mode:"Disabled (1)" LogLinkStateEvent:Log Link State Event:"Enabled (51)" MasterSlave:Gigabit Master Slave Mode:"Auto Detect (0)" NetworkAddress:Locally Administered Address: ReduceSpeedOnPowerDown:Reduce Speed On Power Down:"Disabled (0)" SipsEnabled:System Idle Power Saver:"Disabled (0)" ULPMode:Ultra Low Power Mode:"Enabled (1)" WaitAutoNegComplete:Wait for Link:"Auto Detect (2)" WakeOnLink:Wake on Link Settings:"Disabled (0)" - "Operating System" .Net Framework Version:"2.0,3.0,3.5,4.0,4.7" Boot Device:"\Device\HarddiskVolume1" Internet Browser:"Google Chrome,75.0, Internet Explorer,11.829" Locale:"Spain" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Pro" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"6.50 GB" Physical Memory (Available):"8.26 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.86 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.17134 Build 17134" Virtual Memory (Available):"12.17 GB" Virtual Memory (Total):"22.36 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [02/07/2018]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [02/07/2018]" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2504637:"Microsoft .NET Framework 4 Multi-Targeting Pack [22/10/2018]" 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 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB4230204:"Update [6/28/2018]" KB4338853:"Update [6/28/2018]" KB4343669:"Update [7/23/2018]" KB4456655:"Update [10/3/2018]" KB4465663:"Security Update [11/29/2018]" KB4489907:"Security Update [4/9/2019]" KB4497398:"Security Update [6/20/2019]" KB4503286:"Security Update [6/20/2019]" KB4503308:"Security Update [6/20/2019]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [02/07/2018]" Update for Microsoft Visual Studio 2015 (KB3095681):"Microsoft Visual Studio 2015 [22/10/2018]" - "Processor" - "Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 142 Stepping 10" - "Chipset Name":"Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i5+8350U+CPU+" CPU Speed:"1.70 GHz" Current Voltage:"7. volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00" Driver Path:"C:\WINDOWS\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.17134.765" Ext. Family:"Not Available" Family:"Not Available" FPO:"Not Available" INF:"cpu.inf" INF Section:"IntelPPM_Inst.NT" Install Date:"Not Available" Last Error Code:"Not Available" Level 1 Cache:"4 x 256 KB" Level 2 Cache:"4 x 1024 KB" Level 3 Cache:"6 MB" Load:"57%" Manufacturer:"GenuineIntel" Model:"142" Name:"Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz" Number of Cores:"4" Number of Cores Enabled:"4" Number of Logical Processors:"8" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000806EA" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"10" Version:"Not Available" - "Storage" - "SK hynix SC311 SATA 512GB" Capablities:"Random Access, Supports Writing, SMART Notification" Caption:"SK hynix SC311 SATA 512GB" Cylinder - Total:"62260" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00" Driver Version:"10.0.17134.1" Error Code:"Device is working properly" Firmware Revision:"70000P10" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"SK hynix SC311 SATA 512GB" Name:"\\.\PHYSICALDRIVE0" Partitions:"3" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_SK&PROD_HYNIX\4&1774B54B&0&000200" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"1000206900" Serial Number:"MJ85N763510205Q59" Size:"476.94 GB" Size – Available:"305.89 GB" SMART Attributes:"Self-Test: 80 minutes, OK, Short Self-Test: 2 minutes, OK" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"15876300" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"OS" Serial Number:"E4758D61" Size:"475.20 GB" Size – Available:"305.88 GB" Status:"Not Available" Volume Dirty:"No" - "SMART" 0x01 Raw Read Error Rate:0:"6" 0x05 Reallocated Sector Count:0:"36" 0x09 Power-On Hours:1757:"0" 0x0C Power Cycle Count:631:"20" 0xAE Power-off Retract Count:14:"0" 0xAF Power Loss Protection Failure:0:"0" 0xB0 Erase Fail Count (chip):0:"0" 0xB1 Wear Range Delta:5:"0" 0xB3 Used Reserved Block Count Total:0:"0" 0xB4 Unused Reserved Block Count Total:1282:"0" 0xB5 Program Fail Count Total:0:"0" 0xB6 Erase Fail Count:0:"0" 0xB8 End-to-End Error Detection Count:0:"0" 0xBB Uncorrectable Error Count:0:"0" 0xBC Reported Command Timeouts:91:"0" 0xC2 Internal Device Temperature:32° C:"0" 0xC3 Hardware ECC Recovered:0:"0" 0xC4 Reallocation Count:0:"36" 0xC6 Uncorrectable Sector Count:0:"0" 0xC7 CRC Error Count:0:"0" 0xCC Soft ECC Correction:7265:"0" 0xD4 Shock During Write:9023213:"0" 0xE9 Media Wearout Indicator:100:"0" 0xEA Maximum Erase Count:4698018080:"0" 0xF1 Total LBAs Written:8779892138:"0" 0xF2 Total LBAs Read:18204408014:"0" - "TOSHIBA TransMemory USB Device" Capablities:"Random Access, Supports Writing, Supports Removable Media" Caption:"TOSHIBA TransMemory USB Device" Cylinder - Total:"1885" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00" Driver Version:"10.0.17134.1" Error Code:"Device is working properly" Firmware Revision:"1.00" Heads - Total:"255" Index:"1" INF:"disk.inf" Install Date:"Not Available" Interface Type:"USB" Manufacturer:"(Standard disk drives)" Model:"TOSHIBA TransMemory USB Device" Name:"\\.\PHYSICALDRIVE1" Partitions:"1" Physical Sector Size:"512" PNP Device ID:"USBSTOR\DISK&VEN_TOSHIBA&PROD_TRANSMEMORY&REV_1.00\C2F8957463E6CD4068B9DDC9&0" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" Sectors - Per Track:"63" Sectors - Total:"30282525" Serial Number:"C" Size:"14.44 GB" Size – Available:"5.49 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"480675" - "F:" Availability:"Not Available" Caption:"F:" Compression Method:"Not Compressed" Description:"Removable Disk" File System:"FAT32" Name:"TOSHIBA" Serial Number:"52FE2E08" Size:"14.43 GB" Size – Available:"5.49 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The server {99761EE4-94FF-4765-A4FA-71B8034EF1B2} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "106530690DF7" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "106530690DF7" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Iniciar permission for the COM Server application with CLSID Windows.SecurityCenter.WscBrokerManager and APPID No disponible to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Iniciar permission for the COM Server application with CLSID Windows.SecurityCenter.WscBrokerManager and APPID No disponible to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Iniciar permission for the COM Server application with CLSID Windows.SecurityCenter.WscBrokerManager and APPID No disponible to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Iniciar permission for the COM Server application with CLSID Windows.SecurityCenter.WscBrokerManager and APPID No disponible to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- 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.weareyotta.com. 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 sipdir.online.lync.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Iniciar permission for the COM Server application with CLSID Windows.SecurityCenter.WscBrokerManager and APPID No disponible to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- 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.weareyotta.com. 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 sipdir.online.lync.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Iniciar permission for the COM Server application with CLSID Windows.SecurityCenter.WscBrokerManager and APPID No disponible to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 0x80246013: 2019-05 Actualización de pila de mantenimiento de Windows 10 Version 1803 para sistemas basados en x64 (KB4497398). ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed due to an internal error. Please look into the Group Policy operational log for the specific error message. An attempt will be made to process Group Policy again at the next refresh cycle. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The server Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wekyb3d8bbwe!ContentProcess#{00021404-0001-0000-2592-EA2501000000} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- 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.weareyotta.com. 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 sipdir.online.lync.com. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The activation of the CLSID {E60687F7-01A1-40AA-86AC-DB1CBF673334} timed out waiting for the service wuauserv to stop. ------------------------------------------------------------------- The server {99761EE4-94FF-4765-A4FA-71B8034EF1B2} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The server {99761EE4-94FF-4765-A4FA-71B8034EF1B2} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The Dell Data Vault Service API service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Dell Data Vault Collector service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Dell Data Vault Processor service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9N4CGR6R7PT1-DellInc.DellSupportAssistforPCs. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- Unable to start a DCOM Server: Microsoft.SkypeApp_14.44.40.0_x64__kzf8qxf38zg5c!App.AppX9hm76req7fdyzpbrhbs1g3k95as9j16h.mca as No disponible/No disponible. The error: "298" Happened while starting this command: "C:\Program Files\WindowsApps\Microsoft.SkypeApp_14.44.40.0_x64__kzf8qxf38zg5c\SkypeApp.exe" -ServerName:App.AppXffn3yxqvgawq9fpmnhy90fr3y01d1t5b.mca ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The activation of the CLSID {E60687F7-01A1-40AA-86AC-DB1CBF673334} timed out waiting for the service wuauserv to stop. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The activation of the CLSID {E60687F7-01A1-40AA-86AC-DB1CBF673334} timed out waiting for the service wuauserv to stop. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The server {99761EE4-94FF-4765-A4FA-71B8034EF1B2} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- 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 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 removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- 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 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. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The server {99761EE4-94FF-4765-A4FA-71B8034EF1B2} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- 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.weareyotta.com. 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.weareyotta.com. 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.weareyotta.com. 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.weareyotta.com. 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 processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024001E: 9MVFQ4LMZ6C9-21336V3TApps.MovieMaker-FREE. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {99761EE4-94FF-4765-A4FA-71B8034EF1B2} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ364-MICROSOFT.SKYPEAPP. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- 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 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 específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {99761EE4-94FF-4765-A4FA-71B8034EF1B2} 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. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the 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 {99761EE4-94FF-4765-A4FA-71B8034EF1B2} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The establecido de forma predeterminada en el equipo permission settings do not grant Local Activación permission for the COM Server application with CLSID {0358B920-0AC7-461F-98F4-58E32CD89148} and APPID {3EB3C877-1F16-487C-9050-104DBCD66683} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The establecido de forma predeterminada en el equipo permission settings do not grant Local Activación permission for the COM Server application with CLSID {0358B920-0AC7-461F-98F4-58E32CD89148} and APPID {3EB3C877-1F16-487C-9050-104DBCD66683} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Microsoft Intune from policy Software Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The removal of the assignment of application Rapid7 Insight Agent from policy Windows Insight Installation for Leamington PCs failed. The error was : %%2 ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\SERVICIO LOCAL SID (S-1-5-19) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The server {99761EE4-94FF-4765-A4FA-71B8034EF1B2} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container No disponible SID (No disponible). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy 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 determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ------------------------------------------------------------------- The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. ------------------------------------------------------------------- The específico de la aplicación permission settings do not grant Local Activación permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user OMG\AForner SID (S-1-5-21-533650442-2167683771-662571143-20188) from address LocalHost (con LRPC) running in the application container Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-350187224-1905355452-1037786396-3028148496-2624191407-3283318427-1255436723). This security permission can be modified using the Component Services administrative tool. ------------------------------------------------------------------- The processing of Group Policy failed. Windows could not determine if the user and computer accounts are in the same forest. Ensure the user domain name matches the name of a trusted domain that resides in the same forest as the computer account. ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 7/1/2019, 09:01:50 Machine name: AFORNER Machine Id: {6EBEBE45-7AA0-49B5-AB03-5C3CC2300FCB} Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804) Language: Spanish (Regional Setting: Spanish) System Manufacturer: Dell Inc. System Model: Latitude 5590 BIOS: 1.5.0 (type: UEFI) Processor: Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz (8 CPUs), ~1.9GHz Memory: 16384MB RAM Available OS Memory: 16244MB RAM Page File: 10462MB used, 12438MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) DWM DPI Scaling: UnKnown Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DxDiag Version: 10.00.17134.0001 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Display Tab 2: No problems found. Sound Tab 1: No problems found. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: Intel(R) UHD Graphics 620 Manufacturer: Intel Corporation Chip type: Intel(R) UHD Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_5917&SUBSYS_08171028&REV_07 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 8250 MB Dedicated Memory: 128 MB Shared Memory: 8122 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.585461,0.366711), Green(0.350109,0.579602), Blue(0.162609,0.143078), White Point(0.313000,0.328625) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: unknown Monitor Id: BOE06CB Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: Internal Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd12umd64.dll Driver File Version: 24.20.0100.6170 (English) Driver Version: 24.20.100.6170 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.4 Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: No Blocks Catalog Attributes: Universal:False Declarative:False Driver Attributes: Final Retail Driver Date/Size: 18/06/2018 2:00:00, 2026768 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-1A57-11CF-826B-7328BCC2D535} Vendor ID: 0x8086 Device ID: 0x5917 SubSys ID: 0x08171028 Revision ID: 0x0007 Driver Strong Name: oem58.inf:5f63e534f33a69cc:iKBLD_w10_DS_DC5:24.20.100.6170:pci\ven_8086&dev_5917&subsys_08171028 Rank Of Driver: 00D10001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT DXVA2_ModeVP8_VLD DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 1 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported Card name: Intel(R) UHD Graphics 620 Manufacturer: Intel Corporation Chip type: Intel(R) UHD Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_5917&SUBSYS_08171028&REV_07 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 8250 MB Dedicated Memory: 128 MB Shared Memory: 8122 MB Current Mode: 1366 x 768 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Extend Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.646984,0.333508), Green(0.317883,0.625500), Blue(0.154797,0.061047), White Point(0.313977,0.329602) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: K202HQL Monitor Id: ACR03E0 Native Mode: 1366 x 768(p) (59.790Hz) Output Type: Displayport External Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd12umd64.dll Driver File Version: 24.20.0100.6170 (English) Driver Version: 24.20.100.6170 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.4 Graphics Preemption: Triangle Compute Preemption: Thread Miracast: Supported Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: No Blocks Catalog Attributes: Universal:False Declarative:False Driver Attributes: Final Retail Driver Date/Size: 18/06/2018 2:00:00, 2026768 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-1A57-11CF-826B-7328BCC2D535} Vendor ID: 0x8086 Device ID: 0x5917 SubSys ID: 0x08171028 Revision ID: 0x0007 Driver Strong Name: oem58.inf:5f63e534f33a69cc:iKBLD_w10_DS_DC5:24.20.100.6170:pci\ven_8086&dev_5917&subsys_08171028 Rank Of Driver: 00D10001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT DXVA2_ModeVP8_VLD DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 1 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported ------------- Sound Devices ------------- Description: Speakers / Headphones (Realtek Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0256&SUBSYS_10280817&REV_1000 Manufacturer ID: 1 Product ID: 100 Type: WDM Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.8378 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 22/02/2018 0:00:00, 6169024 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 Array (Realtek Audio) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: RTKVHD64.sys Driver Version: 6.00.0001.8378 (English) Driver Attributes: Final Retail Date and Size: 2/22/2018 16:48:48, 6169024 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 1 --------------------- FriendlyName: Integrated Webcam Category: Camera SymbolicLink: \\?\usb#vid_0c45&pid_6717&mi_00#6&275a5b00&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 Manufacturer: Microsoft HardwareID: USB\VID_0C45&PID_6717&REV_7524&MI_00,USB\VID_0C45&PID_6717&MI_00 DriverDesc: USB Video Device DriverProvider: Microsoft DriverVersion: 10.0.17134.1 DriverDateEnglish: 6/21/2006 00:00:00 DriverDateLocalized: 21/06/2006 0:00:00 Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: Integrated Webcam Parent: USB\VID_0C45&PID_6717\5&946e9eb&0&5 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: n/a MFT0: n/a DMFT: n/a DependentStillCapture: n/a EnablePlatformDMFT: n/a DMFTChain: n/a EnableDshowRedirection: n/a FrameServerEnabled: 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: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x044E, 0x121F FF Driver: n/a Device Name: Intel(R) HID Event Filter Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x8087, 0x0A1E FF Driver: n/a Device Name: Intel(R) HID Event Filter Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x8087, 0x0A1E FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x044E, 0x121F FF Driver: n/a Device Name: Converted Portable Device Control device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0000 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x044E, 0x121F 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: USB Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC31C FF Driver: n/a Device Name: USB Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC31C FF Driver: n/a Device Name: USB Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC31C FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x9D2F | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 11/9/2018 04:49:37, 565048 bytes | +-+ Generic USB Hub | | Vendor/Product ID: 0x0BDA, 0x5411 | | Location: Port_#0002.Hub_#0001 | | Matching Device ID: USB\USB20_HUB | | Service: USBHUB3 | | Driver: USBHUB3.SYS, 11/9/2018 04:49:37, 565048 bytes | | | +-+ USB Composite Device | | | Vendor/Product ID: 0x046D, 0xC31C | | | Location: Port_#0002.Hub_#0003 | | | Matching Device ID: USB\COMPOSITE | | | Service: usbccgp | | | Driver: usbccgp.sys, 4/12/2018 01:33:52, 168864 bytes | | | | | +-+ USB Input Device | | | | Vendor/Product ID: 0x046D, 0xC31C | | | | Location: 0000.0014.0000.002.002.000.000.000.000 | | | | Matching Device ID: USB\Class_03&SubClass_01 | | | | Service: HidUsb | | | | Driver: hidusb.sys, 4/12/2018 01:33:52, 42496 bytes | | | | Driver: hidclass.sys, 4/12/2018 01:33:52, 173568 bytes | | | | Driver: hidparse.sys, 3/6/2019 10:33:02, 46080 bytes | | | | | | | +-+ HID Keyboard Device | | | | | Vendor/Product ID: 0x046D, 0xC31C | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | Service: kbdhid | | | | | Driver: kbdhid.sys, 4/12/2018 01:33:52, 40448 bytes | | | | | Driver: kbdclass.sys, 4/12/2018 01:33:52, 63904 bytes | | | | +-+ USB Input Device | | | Vendor/Product ID: 0x046D, 0xC077 | | | Location: Port_#0003.Hub_#0003 | | | Matching Device ID: USB\Class_03&SubClass_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 4/12/2018 01:33:52, 42496 bytes | | | Driver: hidclass.sys, 4/12/2018 01:33:52, 173568 bytes | | | Driver: hidparse.sys, 3/6/2019 10:33:02, 46080 bytes | | | | | +-+ HID-compliant mouse | | | | Vendor/Product ID: 0x046D, 0xC077 | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | Service: mouhid | | | | Driver: mouhid.sys, 4/12/2018 01:33:52, 33280 bytes | | | | Driver: mouclass.sys, 4/12/2018 01:33:52, 56728 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + Standard PS/2 Keyboard | Matching Device ID: *PNP0303 | Service: i8042prt | Driver: i8042prt.sys, 4/12/2018 01:33:52, 105984 bytes | Driver: kbdclass.sys, 4/12/2018 01:33:52, 63904 bytes | + HID Keyboard Device | Vendor/Product ID: 0x045E, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 4/12/2018 01:33:52, 40448 bytes | Driver: kbdclass.sys, 4/12/2018 01:33:52, 63904 bytes | + HID Keyboard Device | Vendor/Product ID: 0x044E, 0x1212 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 4/12/2018 01:33:52, 40448 bytes | Driver: kbdclass.sys, 4/12/2018 01:33:52, 63904 bytes | + HID-compliant mouse | Vendor/Product ID: 0x044E, 0x1212 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 4/12/2018 01:33:52, 33280 bytes | Driver: mouclass.sys, 4/12/2018 01:33:52, 56728 bytes | + HID-compliant mouse | Vendor/Product ID: 0x044E, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 4/12/2018 01:33:52, 33280 bytes | Driver: mouclass.sys, 4/12/2018 01:33:52, 56728 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 313.2 GB Total Space: 486.6 GB File System: NTFS Model: SK hynix SC311 SATA 512GB -------------- System Devices -------------- Name: Intel(R) Serial IO I2C Host Controller - 9D61 Device ID: PCI\VEN_8086&DEV_9D61&SUBSYS_08171028&REV_21\3&11583659&0&A9 Driver: C:\WINDOWS\system32\DRIVERS\iaLPSS2i_I2C.sys, 30.100.1724.0001 (English), 4/12/2018 01:33:45, 171520 bytes Name: Intel(R) UHD Graphics 620 Device ID: PCI\VEN_8086&DEV_5917&SUBSYS_08171028&REV_07\3&11583659&0&10 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdkmd64.sys, 24.20.0100.6170 (English), 7/24/2018 23:41:44, 13186544 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iglhxs64.vp, 7/24/2018 23:41:46, 4802 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10iumd64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:20, 21499160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd11dxva64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:24, 57337688 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd12dxva64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:30, 58710008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd12umd64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:36, 19580248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxcmrt64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:46, 220528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfx11cmrt64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:46, 218992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdumdim64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:46, 2026768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd9dxva64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:40, 57622744 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdail64.dll, 7/24/2018 23:41:44, 199112 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iga64.dll, 7/24/2018 23:41:16, 2908120 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igc64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:16, 32572704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\UniversalAdapter64.dll, 7/24/2018 23:42:08, 179528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\common_clang64.dll, 4.03.0000.0000 (English), 7/24/2018 23:41:08, 53922336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdfcl64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:44, 810568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdmd64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:44, 3966032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdde64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:44, 452200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10idpp64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:18, 553832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd12ext64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:34, 156104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10iumd32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:18, 20434904 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd11dxva32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:20, 55792288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd12dxva32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:28, 57119608 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd12umd32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:34, 19133752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdumdim32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:46, 1800400 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd9dxva32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:36, 55935928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdail32.dll, 7/24/2018 23:41:44, 172488 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxcmrt32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:46, 186992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfx11cmrt32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:46, 185968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iga32.dll, 7/24/2018 23:41:16, 2467856 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igc32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:16, 29038432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\UniversalAdapter32.dll, 7/24/2018 23:42:08, 261840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\common_clang32.dll, 4.03.0000.0000 (English), 7/24/2018 23:41:06, 39501248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdfcl32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:44, 840136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdmd32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:44, 3066288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdde32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:44, 372456 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd10idpp32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:18, 528680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igd12ext32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:34, 132488 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iglhxo64.vp, 7/24/2018 23:41:46, 40749 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iglhxc64.vp, 7/24/2018 23:41:46, 39700 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iglhxg64.vp, 7/24/2018 23:41:46, 39980 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iglhxo64_dev.vp, 7/24/2018 23:41:46, 40609 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iglhxc64_dev.vp, 7/24/2018 23:41:46, 40316 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iglhxg64_dev.vp, 7/24/2018 23:41:46, 40876 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iglhxa64.vp, 7/24/2018 23:41:46, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\iglhxa64.cpa, 7/24/2018 23:41:46, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\IntelCpHDCPSvc.exe, 24.20.0100.6170 (English), 7/24/2018 23:41:48, 458216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\IntelCpHeciSvc.exe, 9.01.0001.1117 (English), 7/24/2018 23:41:48, 489448 bytes Driver: C:\WINDOWS\system32\cp_resources.bin, 7/24/2018 23:41:12, 1071820 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\difx64.exe, 1.04.0004.0000 (English), 7/24/2018 23:41:12, 155624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxDH.dll, 6.15.0100.6170 (English), 7/24/2018 23:41:46, 1123800 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxDI.dll, 6.15.0100.6170 (English), 7/24/2018 23:41:46, 461768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxLHM.dll, 6.15.0100.6170 (English), 7/24/2018 23:41:46, 2214848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxEM.exe, 6.15.0100.6170 (English), 7/24/2018 23:41:46, 1008616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxCUIServicePS.dll, 7/24/2018 23:41:46, 413128 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxCUIService.exe, 6.15.0100.6170 (English), 7/24/2018 23:41:46, 396776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxDHLib.dll, 1.00.0000.0000 (Invariant Language), 7/24/2018 23:41:46, 123336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxLHMLib.dll, 1.00.0000.0000 (Invariant Language), 7/24/2018 23:41:46, 22464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\GfxUIEx.exe, 6.15.0100.6170 (English), 7/24/2018 23:41:12, 500712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\Gfxv4_0.exe, 8.15.0100.6170 (Spanish), 7/24/2018 23:41:12, 1222120 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\GfxResources.dll, 8.15.0100.6170 (Spanish), 7/24/2018 23:41:12, 9335232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\MetroIntelGenericUIFramework.dll, 1.00.0000.0000 (Spanish), 7/24/2018 23:41:52, 645576 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxCPL.cpl, 7/24/2018 23:41:46, 288704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxDTCM.dll, 6.15.0100.6170 (English), 7/24/2018 23:41:46, 195008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxext.exe, 6.15.0100.6170 (English), 7/24/2018 23:41:46, 343528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxexps.dll, 6.15.0010.3682 (English), 7/24/2018 23:41:46, 55216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\GfxDownloadWrapper.exe, 8.15.0100.6170 (Spanish), 7/24/2018 23:41:12, 140264 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxSDK.exe, 7/24/2018 23:41:46, 1128936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxSDKLib.dll, 1.00.0000.0000 (Invariant Language), 7/24/2018 23:41:46, 99784 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\ColorImageEnhancement.wmv, 7/24/2018 23:41:06, 375173 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\ImageStabilization.wmv, 7/24/2018 23:41:48, 403671 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\FilmModeDetection.wmv, 7/24/2018 23:41:12, 641530 bytes Driver: C:\WINDOWS\system32\igfxCPL.cpl, 7/24/2018 23:41:46, 288704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igfxexps32.dll, 6.15.0010.3682 (English), 7/24/2018 23:41:46, 52680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\ig9icd64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:14, 15420360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\ig9icd32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:14, 12082120 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\OSSCOPYRIGHT, 7/24/2018 23:42:08, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igvk64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:48, 11759104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igvk64.json, 7/24/2018 23:41:48, 137 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\VulkanRT-EULA.rtf, 7/24/2018 23:42:08, 1469 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\VulkanRT-Installer.exe, 1.01.0073.0000 (English), 7/24/2018 23:42:08, 1217216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igvk32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:46, 10667568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igvk32.json, 7/24/2018 23:41:48, 137 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\llvm_release_license.txt, 11/7/2017 11:38:50, 1981 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\readme.txt, 11/7/2017 11:38:52, 9788 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\version.ini, 7/24/2018 23:42:06, 32 bytes Driver: C:\WINDOWS\SysWow64\Intel_OpenCL_ICD32.dll, 2.01.0001.0000 (English), 7/24/2018 23:41:48, 119752 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\task_executor32.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:06, 398792 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\OclCpuBackend32.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:04, 12883912 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\intelocl32.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:04, 1362888 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\cpu_device32.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:02, 565704 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8.rtl, 7/24/2018 23:42:02, 2527472 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.o, 7/24/2018 23:42:02, 394116 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.rtl, 7/24/2018 23:42:02, 978088 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9.rtl, 7/24/2018 23:42:02, 2486680 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.o, 7/24/2018 23:42:02, 381364 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.rtl, 7/24/2018 23:42:02, 977952 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9.rtl, 7/24/2018 23:42:02, 1498332 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.o, 7/24/2018 23:42:02, 327948 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.rtl, 7/24/2018 23:42:02, 870628 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clang_compiler32.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:02, 2047944 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_n8.dll, 3.06.0002.0000 (English), 7/24/2018 23:42:06, 7164872 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_g9.dll, 3.06.0002.0000 (English), 7/24/2018 23:42:06, 6313416 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_s9.dll, 3.06.0002.0000 (English), 7/24/2018 23:42:08, 6120904 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\ocltbbmalloc32.dll, 2018.00.2018.0412 (Spanish), 7/24/2018 23:42:06, 105136 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\ocltbb32.dll, 2018.00.2018.0412 (Spanish), 7/24/2018 23:42:06, 218288 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\common\clbltfnshared.rtl, 7/24/2018 23:42:02, 1315452 bytes Driver: C:\WINDOWS\system32\Intel_OpenCL_ICD64.dll, 2.01.0001.0000 (English), 7/24/2018 23:41:48, 144840 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\task_executor64.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:06, 495552 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\OclCpuBackend64.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:04, 17409992 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\intelocl64.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:04, 1748424 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\cpu_device64.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:04, 749000 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8.rtl, 7/24/2018 23:42:02, 2536784 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.o, 7/24/2018 23:42:02, 421600 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.rtl, 7/24/2018 23:42:02, 1053120 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9.rtl, 7/24/2018 23:42:02, 2495784 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.o, 7/24/2018 23:42:02, 401264 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.rtl, 7/24/2018 23:42:02, 1052984 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9.rtl, 7/24/2018 23:42:02, 1507348 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.o, 7/24/2018 23:42:02, 346040 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.rtl, 7/24/2018 23:42:02, 945776 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clang_compiler64.dll, 7.06.0000.0716 (English), 7/24/2018 23:42:02, 2741704 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_h8.dll, 3.06.0002.0000 (English), 7/24/2018 23:42:06, 7455680 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_e9.dll, 3.06.0002.0000 (English), 7/24/2018 23:42:06, 6800840 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_l9.dll, 3.06.0002.0000 (English), 7/24/2018 23:42:06, 6612448 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\ocltbbmalloc64.dll, 2018.00.2018.0412 (Spanish), 7/24/2018 23:42:06, 143536 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\ocltbb64.dll, 2018.00.2018.0412 (Spanish), 7/24/2018 23:42:06, 280760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\IntelOpenCL32.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:48, 1203656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdrcl32.dll, 7/24/2018 23:41:44, 4306888 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\IntelOpenCL64.dll, 24.20.0100.6170 (English), 7/24/2018 23:41:48, 1564104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igdrcl64.dll, 7/24/2018 23:41:46, 4820936 bytes Driver: C:\WINDOWS\SysWow64\libEGL.dll, 7/24/2018 23:41:48, 148960 bytes Driver: C:\WINDOWS\SysWow64\libGLESv1_CM.dll, 7/24/2018 23:41:48, 133576 bytes Driver: C:\WINDOWS\SysWow64\libGLESv2.dll, 7/24/2018 23:41:48, 167904 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw32.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:48, 17611256 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin32_hw.dll, 1.18.0005.0010 (English), 7/24/2018 23:41:52, 11858376 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_32.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:54, 2638896 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_32.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:54, 2497480 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_32.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:54, 2651984 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_32.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:56, 2646664 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_32.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:54, 2493704 bytes Driver: C:\Program Files\Intel\Media SDK\c_32.cpa, 11/7/2017 11:38:10, 1361159 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_32.vp, 7/24/2018 23:41:12, 1125 bytes Driver: C:\Program Files\Intel\Media SDK\dev_32.vp, 7/24/2018 23:41:12, 57143 bytes Driver: C:\Program Files\Intel\Media SDK\he_32.vp, 7/24/2018 23:41:12, 80593 bytes Driver: C:\Program Files\Intel\Media SDK\mj_32.vp, 7/24/2018 23:41:56, 75825 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_32.vp, 7/24/2018 23:41:12, 82057 bytes Driver: C:\Program Files\Intel\Media SDK\vp9e_32.vp, 7/24/2018 23:42:08, 81684 bytes Driver: C:\Program Files\Intel\Media SDK\vr360sdk32.dll, 7/24/2018 23:42:08, 599488 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw64.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:50, 18531424 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin64_hw.dll, 1.18.0005.0010 (English), 7/24/2018 23:41:52, 22139336 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_64.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:54, 3185496 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_64.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:54, 3016136 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_64.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:54, 3210040 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_64.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:56, 3199088 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_64.dll, 8.18.0005.0010 (English), 7/24/2018 23:41:54, 2997360 bytes Driver: C:\Program Files\Intel\Media SDK\c_64.cpa, 11/7/2017 11:38:10, 1376256 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_64.vp, 7/24/2018 23:41:12, 1125 bytes Driver: C:\Program Files\Intel\Media SDK\dev_64.vp, 7/24/2018 23:41:12, 56359 bytes Driver: C:\Program Files\Intel\Media SDK\he_64.vp, 7/24/2018 23:41:12, 13591 bytes Driver: C:\Program Files\Intel\Media SDK\mj_64.vp, 7/24/2018 23:41:56, 13343 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_64.vp, 7/24/2018 23:41:12, 14131 bytes Driver: C:\Program Files\Intel\Media SDK\vp9e_64.vp, 7/24/2018 23:42:08, 14026 bytes Driver: C:\Program Files\Intel\Media SDK\vr360sdk64.dll, 7/24/2018 23:42:08, 598472 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 7/24/2018 23:41:48, 191816 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 7/24/2018 23:41:48, 163888 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ki128602.inf_amd64_6ff790822fd674ab\igxpco64.dll, 1.03.0025.0000 (English), 7/24/2018 23:41:48, 234952 bytes Name: Intel(R) Chipset SATA/PCIe RST Premium Controller Device ID: PCI\VEN_8086&DEV_282A&SUBSYS_08171028&REV_21\3&11583659&0&B8 Driver: C:\WINDOWS\system32\DRIVERS\iaStorAC.sys, 16.08.0002.1002 (English), 3/7/2019 19:30:26, 1094000 bytes Driver: C:\WINDOWS\system32\DRIVERS\iaStorAfs.sys, 16.08.0002.1002 (English), 3/7/2019 19:30:26, 72560 bytes Driver: C:\WINDOWS\system32\iaStorAfsService.exe, 16.08.0002.1002 (English), 3/7/2019 19:30:26, 2832240 bytes Driver: C:\WINDOWS\system32\iaStorAfsNative.exe, 16.08.0002.1002 (English), 3/7/2019 19:30:26, 219504 bytes Driver: C:\WINDOWS\system32\Optane.dll, 16.08.0002.1002 (English), 3/7/2019 19:30:26, 112496 bytes Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O PCI Express Root Port #1 - 9D10 Device ID: PCI\VEN_8086&DEV_9D10&SUBSYS_08171028&REV_F1\3&11583659&0&E0 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.17134.0677 (English), 3/14/2019 10:56:59, 375096 bytes Name: Intel(R) Management Engine Interface Device ID: PCI\VEN_8086&DEV_9D3A&SUBSYS_08171028&REV_21\3&11583659&0&B0 Driver: C:\WINDOWS\system32\DRIVERS\TeeDriverW8x64.sys, 1815.12.0000.2021 (English), 7/15/2018 17:52:54, 228992 bytes Name: Mobile 7th Generation Intel(R) Processor Family I/O LPC Controller (U with iHDCP2.2 Premium) - 9D4E Device ID: PCI\VEN_8086&DEV_9D4E&SUBSYS_08171028&REV_21\3&11583659&0&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.17134.0001 (English), 4/12/2018 01:33:49, 18848 bytes Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O Thermal subsystem - 9D31 Device ID: PCI\VEN_8086&DEV_9D31&SUBSYS_08171028&REV_21\3&11583659&0&A2 Driver: n/a Name: Realtek PCIE CardReader Device ID: PCI\VEN_10EC&DEV_525A&SUBSYS_08171028&REV_01\00000001004CE00000 Driver: C:\WINDOWS\system32\DRIVERS\RtsPer.sys, 10.00.15063.21300 (English), 5/16/2017 03:47:02, 782816 bytes Driver: C:\WINDOWS\SysWOW64\sda\SDRTCPRM.dll, 1.23.9600.0000 (English), 7/14/2016 19:32:28, 134144 bytes Driver: C:\WINDOWS\RtCRU64.exe, 1.13.0000.0000 (English), 7/14/2016 19:23:08, 4332032 bytes Driver: C:\WINDOWS\SysWOW64\RsCRIcon.dll, 1.10.0000.0000 (English), 7/14/2016 19:40:16, 9891328 bytes Driver: C:\WINDOWS\system32\RtCRX64.dll, 1.11.9600.0000 (Chinese (Simplified)), 7/14/2016 19:27:52, 84480 bytes Name: Intel(R) Dual Band Wireless-AC 8265 Device ID: PCI\VEN_8086&DEV_24FD&SUBSYS_00508086&REV_78\7470FDFFFFBC5EEE00 Driver: C:\Program Files\Intel\Wireless\WUSetupLauncher.exe, 5/3/2019 07:46:08, 146680 bytes Driver: C:\Program Files\Intel\Wireless\Setup.exe, , 0 bytes Driver: C:\Program Files\Intel\Wireless\setup.xml, , 0 bytes Driver: C:\Program Files\Intel\Wireless\Data\WiFi.msi, , 0 bytes Driver: C:\Program Files\Intel\Wireless\Data\Driver.msi, , 0 bytes Driver: C:\WINDOWS\system32\DRIVERS\Netwtw06.sys, 20.70.0009.0001 (English), 5/3/2019 07:46:08, 8841312 bytes Driver: C:\WINDOWS\system32\DRIVERS\Netwfw06.dat, 5/3/2019 02:25:46, 2665408 bytes Driver: C:\WINDOWS\system32\IntelWifiIhv06.dll, 20.70.0009.0001 (English), 5/3/2019 07:46:06, 1116256 bytes Driver: C:\WINDOWS\system32\Netwuw06.dll, 15.06.0000.0000 (English), 5/3/2019 07:46:08, 2688224 bytes Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O SMBUS - 9D23 Device ID: PCI\VEN_8086&DEV_9D23&SUBSYS_08171028&REV_21\3&11583659&0&FC Driver: n/a Name: Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft) Device ID: PCI\VEN_8086&DEV_9D2F&SUBSYS_08171028&REV_21\3&11583659&0&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.17134.0001 (English), 4/12/2018 01:33:52, 434592 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.17134.0001 (English), 4/12/2018 01:33:52, 123576 bytes Name: Intel(R) Dynamic Platform and Thermal Framework Processor Participant Device ID: PCI\VEN_8086&DEV_1903&SUBSYS_08171028&REV_08\3&11583659&0&20 Driver: C:\WINDOWS\system32\DRIVERS\dptf_cpu.sys, 8.03.10207.5567 (English), 11/22/2017 02:20:50, 69536 bytes Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_9D71&SUBSYS_08171028&REV_21\3&11583659&0&FB Driver: C:\WINDOWS\system32\DRIVERS\IntcAudioBus.sys, 9.21.0000.2789 (English), 9/14/2017 00:11:54, 237656 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.17134.0001 (English), 4/12/2018 01:33:46, 98304 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.17134.0001 (English), 4/12/2018 01:33:46, 379392 bytes Name: Intel(R) Serial IO I2C Host Controller - 9D60 Device ID: PCI\VEN_8086&DEV_9D60&SUBSYS_08171028&REV_21\3&11583659&0&A8 Driver: C:\WINDOWS\system32\DRIVERS\iaLPSS2i_I2C.sys, 30.100.1724.0001 (English), 4/12/2018 01:33:45, 171520 bytes Name: Intel(R) Xeon(R) E3 - 1200 v6/7th Gen Intel(R) Core(TM) Host Bridge/DRAM Registers - 5914 Device ID: PCI\VEN_8086&DEV_5914&SUBSYS_08171028&REV_08\3&11583659&0&00 Driver: n/a Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O PMC - 9D21 Device ID: PCI\VEN_8086&DEV_9D21&SUBSYS_08171028&REV_21\3&11583659&0&FA Driver: n/a Name: Intel(R) Ethernet Connection (4) I219-LM Device ID: PCI\VEN_8086&DEV_15D7&SUBSYS_08171028&REV_21\3&11583659&0&FE Driver: n/a Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O PCI Express Root Port #3 - 9D12 Device ID: PCI\VEN_8086&DEV_9D12&SUBSYS_08171028&REV_F1\3&11583659&0&E2 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.17134.0677 (English), 3/14/2019 10:56:59, 375096 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.17134.0001 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.17134.0001 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.17134.0001 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.17134.0001 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.17134.0001 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.17134.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.17134.0471 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.17134.0001 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.17134.0001 DV Muxer,0x00400000,0,0,qdv.dll,10.00.17134.0001 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.17134.0001 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.17134.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.17134.0001 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.17134.0001 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.17134.0001 WavesFilter,0x00200000,1,1,WavesFilter64.dll,1.00.0002.0000 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.17134.0471 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.17134.0001 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.17134.0001 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.17134.0001 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.17134.0001 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.17134.0001 VSDC Video Decoder,0x0080a000,1,1,mslvddsfilter4.ax,4.00.0001.0180 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.17134.0001 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.17134.0001 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.17134.0001 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.17134.0001 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.17134.0112 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.17134.0001 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.17134.0001 DV Splitter,0x00600000,1,2,qdv.dll,10.00.17134.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.17134.0001 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.17134.0112 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.17134.0001 Video Renderer,0x00800001,1,0,quartz.dll,10.00.17134.0001 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.17134.0001 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.17134.0001 Video Renderer,0x00400000,1,0,quartz.dll,10.00.17134.0001 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.17134.0001 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.17134.0001 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax, File writer,0x00200000,1,0,qcap.dll,10.00.17134.0001 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.17134.0001 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.17134.0001 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.17134.0112 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.17134.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.17134.0001 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.17134.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.17134.0001 Null Renderer,0x00200000,1,0,qedit.dll,10.00.17134.0001 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.17134.0001 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.17134.0001 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.17134.0001 Smart Tee,0x00200000,1,2,qcap.dll,10.00.17134.0001 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.17134.0001 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.17134.0001 Wave Parser,0x00400000,1,1,quartz.dll,10.00.17134.0001 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.17134.0001 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.17134.0001 File stream renderer,0x00400000,1,1,quartz.dll,10.00.17134.0001 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.17134.0471 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.17134.0001 AVI Mux,0x00200000,1,0,qcap.dll,10.00.17134.0001 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.17134.0001 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.17134.0001 File Source (URL),0x00400000,0,1,quartz.dll,10.00.17134.0001 Video Out,0x00200000,0,1,mslvvdsfilter4.ax, Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.17134.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.17134.0320 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.17134.0001 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.17134.0001 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.17134.0001 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.17134.0001 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.17134.0001 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.17134.0001 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.17134.0001 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.17134.0001 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.17134.0001 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.17134.0001 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.17134.0001 PCM,0x00200000,1,1,quartz.dll,10.00.17134.0001 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.17134.0001 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.17134.0001 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.17134.0001 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.17134.0001 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.17134.0001 Audio Capture Sources: Microphone Array (Realtek Audio),0x00200000,0,0,qcap.dll,10.00.17134.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.17134.0799 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.17134.0799 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.17134.0799 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.17134.0001 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.17134.0001 WDM Streaming Capture Devices: Integrated Webcam,0x00200000,1,1,ksproxy.ax,10.00.17134.0001 Realtek HD Audio Front Mic input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001 Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001 Realtek HD Audio Mic Array input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001 WDM Streaming Rendering Devices: Realtek HD Audio output with SST,0x00200000,1,1,ksproxy.ax,10.00.17134.0001 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.17134.0001 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.17134.0001 Video Capture Sources: Integrated Webcam,0x00200000,1,1,ksproxy.ax,10.00.17134.0001 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.17134.0001 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.17134.0001 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.17134.0001 BDA CP/CA Filters: Decrypt/Tag,0x00600000,1,1,msvidctl.dll,6.05.17134.0001 Encrypt/Tag,0x00200000,0,0,, PTFilter,0x00200000,0,0,, XDS Codec,0x00200000,0,0,, WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.17134.0001 Audio Renderers: Speakers / Headphones (Realtek Audio),0x00200000,1,0,quartz.dll,10.00.17134.0001 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.17134.0001 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.17134.0001 DirectSound: Speakers / Headphones (Realtek Audio),0x00200000,1,0,quartz.dll,10.00.17134.0001 ---------------------------- Preferred DirectShow Filters ---------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred] , [, ] MEDIASUBTYPE_MPEG1Payload, MPEG Video Decoder, CLSID_CMpegVideoCodec MEDIASUBTYPE_MPEG1Packet, MPEG Video Decoder, CLSID_CMpegVideoCodec 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 {6C737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64697678-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {64687664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {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 MEDIASUBTYPE_MJPG, MJPEG Decompressor, CLSID_MjpegDec {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 {20637664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec 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_MPEG1AudioPayload, MPEG Audio Decoder, CLSID_CMpegAudioCodec WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject WMMEDIASUBTYPE_WMSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject --------------------------- 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, 8.18.0005.0010 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.17134.0471 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.17134.0001 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.17134.0001 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.17134.0471 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.17134.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.17134.0471 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.17134.0001 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.17134.0001 Microsoft WebM MF VP8 Decoder Transform, {E3AAF548-C9A4-4C6E-234D-5ADA374B0000}, 0x1, MSVP9DEC.dll, 10.00.17134.0471 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.17134.0001 MPEG2VideoExtension HEVCVideoExtension Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 8.18.0005.0010 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 8.18.0005.0010 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.17134.0001 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.17134.0001 Microsoft MF VPX Encoder Transform, {AEB6C755-2546-4881-82CC-E15AE5EBFF3D}, 0x1, MSVPXENC.dll, 10.00.17134.0766 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.17134.0001 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.17134.0001 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.17134.0112 HEVCVideoExtensionEncoder Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.17134.0001 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.17134.0001 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.17134.0829 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.17134.0001 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.17134.0001 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.17134.0799 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.17134.0081 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.17134.0001 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.17134.0001 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.17134.0471 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.17134.0799 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.17134.0799 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.17134.0001 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.17134.0001 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.17134.0001 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.17134.0471 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.17134.0001 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.17134.0799 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.17134.0799 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.17134.0001 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.17134.0001 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.17134.0799 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.17134.0001 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.17134.0001 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.17134.0001 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.17134.0799 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.17134.0001 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.17134.0001 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.17134.0001 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.17134.0112 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.17134.0001 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.17134.0001 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.17134.0001 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.17134.0001 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.17134.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.17134.0137 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.17134.0799 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.17134.0471 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableEncoders = 1 EnableDecoders = 1 ------------------------------------- Media Foundation Byte Stream Handlers ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] .3g2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .ac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .adt, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .am?, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler .amr, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler, Preferred .asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred .dvr-ms, {65964407-A5D8-4060-85B0-1CCD63F768E2}, dvr-ms Byte Stream Handler, Preferred .dvr-ms, {A8721937-E2FB-4D7A-A9EE-4EB08C890B6E}, MF SBE Source ByteStreamHandler .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 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] , [, ] {E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B} MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} {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 {30395056-0000-0010-8000-00AA00389B71}, Microsoft WebM MF VP8 Decoder Transform, {E3AAF548-C9A4-4C6E-234D-5ADA374B0000} {30385056-0000-0010-8000-00AA00389B71}, Microsoft WebM MF VP8 Decoder Transform, {E3AAF548-C9A4-4C6E-234D-5ADA374B0000} 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} 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} WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject 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} ------------------------------------- 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 1763113031526682511, type 5 Event Name: POFContextAppCrash Response: No disponible Cab Id: 0 Problem signature: P1: DellInc.DellSupportAssistforPCs_3.2.5.0_x64__htrsf667h5kn2 P2: praid:App P3: 3.2.5.0 P4: 0x80131537 P5: 37aefa3434a7aa47cd5da2420833ff26 P6: P7: P8: P9: P10: +++ WER1 +++: Fault bucket , type 0 Event Name: POFContextAppCrash Response: Not available Cab Id: 0 Problem signature: P1: DellInc.DellSupportAssistforPCs_3.2.5.0_x64__htrsf667h5kn2 P2: praid:App P3: 3.2.5.0 P4: 0x80131537 P5: 37aefa3434a7aa47cd5da2420833ff26 P6: P7: P8: P9: P10: +++ WER2 +++: Fault bucket , type 0 Event Name: POFContextAppCrash Response: Not available Cab Id: 0 Problem signature: P1: DellInc.DellSupportAssistforPCs_3.2.5.0_x64__htrsf667h5kn2 P2: praid:App P3: 3.2.5.0 P4: 0x80131537 P5: 37aefa3434a7aa47cd5da2420833ff26 P6: P7: P8: P9: P10: +++ WER3 +++: Fault bucket 1208365258242900028, type 5 Event Name: StoreAgentDownloadFailure1 Response: No disponible Cab Id: 0 Problem signature: P1: Update;ScanForUpdates P2: 8024001e P3: 17134 P4: 829 P5: Windows.Desktop P6: N P7: P8: P9: P10: +++ WER4 +++: Fault bucket 1859337180279528351, type 5 Event Name: StoreAgentDownloadFailure1 Response: No disponible Cab Id: 0 Problem signature: P1: Update;ScanForUpdates P2: 8024001e P3: 17134 P4: 829 P5: Windows.Desktop P6: W P7: P8: P9: P10: +++ WER5 +++: Fault bucket 2123983417755583285, type 5 Event Name: StoreAgentDownloadFailure1 Response: No disponible Cab Id: 0 Problem signature: P1: Update;ScanForUpdates P2: 8024001e P3: 17134 P4: 829 P5: Windows.Desktop P6: L P7: P8: P9: P10: +++ WER6 +++: Fault bucket , type 0 Event Name: WindowsUpdateFailure3 Response: No disponible Cab Id: 0 Problem signature: P1: 10.0.17134.799 P2: 80073d02 P3: DBD4DB2A-C924-4A94-A5EE-FF57E2237AEA P4: Install P5: 1 P6: 0 P7: 0 P8: Update;ScanForUpdates P9: {855E8A7C-ECB4-4CA3-B045-1DFA50104289} P10: 0 +++ WER7 +++: Fault bucket , type 0 Event Name: StoreAgentDownloadFailure1 Response: No disponible Cab Id: 0 Problem signature: P1: Update;ScanForUpdates P2: 8024001e P3: 17134 P4: 829 P5: Windows.Desktop P6: N P7: P8: P9: P10: +++ WER8 +++: Fault bucket , type 0 Event Name: StoreAgentDownloadFailure1 Response: No disponible Cab Id: 0 Problem signature: P1: Update;ScanForUpdates P2: 8024001e P3: 17134 P4: 829 P5: Windows.Desktop P6: W P7: P8: P9: P10: +++ WER9 +++: Fault bucket , type 0 Event Name: StoreAgentDownloadFailure1 Response: No disponible Cab Id: 0 Problem signature: P1: Update;ScanForUpdates P2: 8024001e P3: 17134 P4: 829 P5: Windows.Desktop P6: L P7: P8: P9: P10: ...#SSU#...