# SSU Scan Information
Scan Info:
 Version:"2.5.0.15"
 Date:"12.05.2019"
 Time:"00:01:11.6875186"

# Scanned Hardware
Computer:
          BaseBoard Manufacturer:"LENOVO"
          BIOS Mode:"Legacy"
          BIOS Version/Date:"LENOVO N1EET86W (1.59 ) , 08/28/2019"
          CD or DVD:"ELBY CLONEDRIVE SCSI CdRom Device"
          Embedded Controller Version:"1.18"
          Platform Role:"Mobile"
          Processor:"Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz , GenuineIntel"
          Secure Boot State:"Not Available"
          SMBIOS Version:"2.8"
          Sound Card:"Realtek High Definition Audio"
          Sound Card:"USB Audio Device"
          System Manufacturer:"LENOVO"
          System Model:"20EQS1KV00"
          System SKU:"LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50"
          System Type:"x64-based PC"
          - "Display"
               Intel ® Graphics Driver Version:"26.20.100.7106"
               - "Intel(R) HD Graphics 530"
                    Adapter Compatibility:"Intel Corporation"
                    Adapter DAC Type:"Internal"
                    Adapter RAM:"1,00 GB"
                    Availability:"Running or Full Power"
                    Bits Per Pixel:"32"
                    - "Caption":"Intel(R) HD Graphics 530"
                         Link:"http://www.intel.com/content/www/us/en/search.html?keyword=HD+Graphics+530"
                    CoInstallers:"nvdispgenco6443194.dll,NvGenericCoInstall,nvdispco6443194.dll,NVDisplayCoInstall"
                    Color Table Entries:"4294967296"
                    Dedicated Video Memory:"Not Available"
                    Driver:"igdkmd64.sys"
                    Driver Date:"08.07.2019 02:00"
                    Driver Path:"C:\Windows\system32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdkmd64.sys"
                    Driver Provider:"Intel Corporation"
                    Driver Version:"26.20.100.7106"
                    INF:"oem136.inf"
                    INF Section:"iSKLD_w10_DS"
                    Install Date:"Not Available"
                    Installed Drivers:"C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd12umd64.dll"
                    Last Error Code:"Not Available"
                    Last Error Code Description:"Not Available"
                    Last Reset:"Not Available"
                    Location:"PCI bus 0, device 2, function 0"
                    Manufacturer:"Intel Corporation"
                    Microsoft DirectX* Version:"DirectX 12"
                    Monochrome:"No"
                    Number of Colors:"4294967296"
                    Number of Video Pages:"Not Available"
                    PNP Device ID:"PCI\VEN_8086&DEV_191B&SUBSYS_222E17AA&REV_06\3&B1BFB68&0&10"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"Not Available"
                    Refresh Rate - Current:"60 Hz"
                    Refresh Rate - Maximum:"60 Hz"
                    Refresh Rate - Minimum:"60 Hz"
                    Resolution:"1920 X 1080"
                    Scan Mode:"Noninterlaced"
                    Service Name:"igfx"
                    Status:"OK"
                    Video Architecture:"VGA"
                    Video Memory:"Unknown"
                    Video Processor:"Intel(R) HD Graphics Family"
               - "NVIDIA Quadro M1000M"
                    Adapter Compatibility:"NVIDIA"
                    Adapter DAC Type:"Integrated RAMDAC"
                    Adapter RAM:"2,00 GB"
                    Availability:"Running or Full Power"
                    Bits Per Pixel:"32"
                    Caption:"NVIDIA Quadro M1000M"
                    CoInstallers:"nvdispgenco6443194.dll,NvGenericCoInstall,nvdispco6443194.dll,NVDisplayCoInstall"
                    Color Table Entries:"4294967296"
                    Dedicated Video Memory:"Not Available"
                    Driver:"nvlddmkm.sys"
                    Driver Date:"09.19.2019 02:00"
                    Driver Path:"C:\Windows\system32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvlddmkm.sys"
                    Driver Provider:"NVIDIA"
                    Driver Version:"26.21.14.3194"
                    INF:"oem175.inf"
                    INF Section:"Section066"
                    Install Date:"Not Available"
                    Installed Drivers:"C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll"
                    Last Error Code:"Not Available"
                    Last Error Code Description:"Not Available"
                    Last Reset:"Not Available"
                    Location:"PCI bus 1, device 0, function 0"
                    Manufacturer:"NVIDIA"
                    Microsoft DirectX* Version:"DirectX 12"
                    Monochrome:"No"
                    Number of Colors:"4294967296"
                    Number of Video Pages:"Not Available"
                    PNP Device ID:"PCI\VEN_10DE&DEV_13B1&SUBSYS_222E17AA&REV_A2\4&26BA905&0&0008"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"Not Available"
                    Refresh Rate - Current:"59 Hz"
                    Refresh Rate - Maximum:"60 Hz"
                    Refresh Rate - Minimum:"50 Hz"
                    Resolution:"1920 X 1200"
                    Scan Mode:"Noninterlaced"
                    Service Name:"nvlddmkm"
                    Status:"OK"
                    Video Architecture:"VGA"
                    Video Memory:"Unknown"
                    Video Processor:"Quadro M1000M"
          - "Memory"
               Physical Memory (Available):"18,60 GB"
               Physical Memory (Installed):"32 GB"
               Physical Memory (Total):"31,38 GB"
               - "BANK 0"
                    Capacity:"8 GB"
                    Channel:"ChannelA-DIMM0"
                    Configured Clock Speed:"2133 MHz"
                    Configured Voltage:"1200 millivolts"
                    Data Width:"64 bits"
                    Form Factor:"SODIMM"
                    Interleave Position:"Not Available"
                    Manufacturer:"Micron"
                    Maximum Voltage:"Not Available"
                    Memory Type:"Unknown"
                    Minimum Voltage:"Not Available"
                    Part Number:"16ATF1G64HZ-2G1A2"
                    Serial Number:"12E899C0"
                    Status:"Not Available"
                    Type:"Synchronous"
               - "BANK 1"
                    Capacity:"8 GB"
                    Channel:"ChannelA-DIMM1"
                    Configured Clock Speed:"2133 MHz"
                    Configured Voltage:"1200 millivolts"
                    Data Width:"64 bits"
                    Form Factor:"SODIMM"
                    Interleave Position:"Not Available"
                    Manufacturer:"SK Hynix"
                    Maximum Voltage:"Not Available"
                    Memory Type:"Unknown"
                    Minimum Voltage:"Not Available"
                    Part Number:"HMA81GS6AFR8N-UH"
                    Serial Number:"2B8AAD75"
                    Status:"Not Available"
                    Type:"Synchronous"
               - "BANK 2"
                    Capacity:"8 GB"
                    Channel:"ChannelB-DIMM0"
                    Configured Clock Speed:"2133 MHz"
                    Configured Voltage:"1200 millivolts"
                    Data Width:"64 bits"
                    Form Factor:"SODIMM"
                    Interleave Position:"Not Available"
                    Manufacturer:"Micron"
                    Maximum Voltage:"Not Available"
                    Memory Type:"Unknown"
                    Minimum Voltage:"Not Available"
                    Part Number:"16ATF1G64HZ-2G1A2"
                    Serial Number:"12E899A6"
                    Status:"Not Available"
                    Type:"Synchronous"
               - "BANK 3"
                    Capacity:"8 GB"
                    Channel:"ChannelB-DIMM1"
                    Configured Clock Speed:"2133 MHz"
                    Configured Voltage:"1200 millivolts"
                    Data Width:"64 bits"
                    Form Factor:"SODIMM"
                    Interleave Position:"Not Available"
                    Manufacturer:"SK Hynix"
                    Maximum Voltage:"Not Available"
                    Memory Type:"Unknown"
                    Minimum Voltage:"Not Available"
                    Part Number:"HMA81GS6AFR8N-UH"
                    Serial Number:"2B8AAAE9"
                    Status:"Not Available"
                    Type:"Synchronous"
          - "Motherboard"
               Availability:"Running or Full Power"
               BIOS:"N1EET86W (v1.59 ), LENOVO - 0"
               Caption:"Motherboard"
               - "Chipset":"Intel(R) 100 Series/C230 Series"
                    Link:"http://www.intel.com/content/www/us/en/search.html?keyword=100+Series%2fC230+Series"
               Date:"08.28.2019 02:00"
               Install Date:"Not Available"
               Last Error Code:"Not Available"
               Last Error Code Description:"Not Available"
               Manufacturer:"LENOVO"
               Model:"Not Available"
               Part Number:"Not Available"
               PNP Device ID:"ACPI\PNP0C01\2&DABA3FF&0"
               Power Management Capabilities:"Not Available"
               Power Management Supported:"Not Available"
               Product:"20EQS1KV00"
               Serial Number:"L1HF66N0066"
               Status:"OK"
               Version:"SDK0J40697 WIN"
          - "Networking"
               Intel ® Network Connections Install Options:"ANS,DMIX"
               Intel ® Network Connections Version:"24.3.0.6"
               Intel ® PROSet/Wireless Software Version:"21.30.2.0"
               - "Bluetooth Device (Personal Area Network)"
                    Availability:"Running or Full Power"
                    Caption:"Bluetooth Device (Personal Area Network)"
                    CoInstallers:"Not Available"
                    Default IP Gateway:"Not Available"
                    DHCP Enabled:"Yes"
                    DHCP Lease Expires:"Not Available"
                    DHCP Lease Obtained:"Not Available"
                    DHCP Server:"Not Available"
                    Driver:"bthpan.sys"
                    Driver Date:"06.21.2006 12:00"
                    Driver Path:"C:\Windows\system32\drivers\bthpan.sys"
                    Driver Provider:"Microsoft"
                    Driver Version:"10.0.17134.1"
                    Index:"0005"
                    INF:"bthpan.inf"
                    INF Section:"BthPan.Install"
                    Install Date:"Not Available"
                    Installed:"Yes"
                    IP Address:"Not Available"
                    IP Subnet:"Not Available"
                    Last Error Code:"Not Available"
                    Last Error Code Description:"Not Available"
                    Last Reset:"12.02.2019 09:29"
                    Location:"Not Available"
                    MAC Address:"Not Available"
                    Manufacturer:"Microsoft"
                    Media Type:
                    Net Connection ID:"Bluetooth Network Connection"
                    NetCfgInstanceId:"{769CA466-EC33-4ABE-8239-8CA340E4DEB1}"
                    Number of VLANs:"0"
                    PNP Device ID:"BTH\MS_BTHPAN\6&3A1BC7B9&0&2"
                    Port:"Not Available"
                    Power Management (Low Power):"Not Available"
                    Power Management (Wake On LAN):"Not Available"
                    Power Management (Wake on Magic Packet):"Not Available"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Product Type:"Bluetooth Device (Personal Area Network)"
                    Service Name:"BthPan"
                    Status:"Device is disabled."
                    Team Name:"Not in a team"
                    Temperature:
                    Type:"Not Available"
                    - "Service Bindings"
                         Client for Microsoft Networks:
                         File and Printer Sharing for Microsoft Networks:
                         Internet Protocol Version 4 (TCP/IPv4):
                         Internet Protocol Version 6 (TCP/IPv6):
                         Link-Layer Topology Discovery Mapper I/O Driver:
                         Link-Layer Topology Discovery Responder:
                         Microsoft LLDP Protocol Driver:
                         Npcap Packet Driver (NPCAP):
                         Npcap Packet Driver (NPCAP) (Wi-Fi):
                         Npcap Packet Driver (NPF):
                         Npcap Packet Driver (NPF) (Wi-Fi):
               - "D-Link DUB-E100 USB2.0 to Fast Ethernet Adapter"
                    Availability:"Running or Full Power"
                    Caption:"D-Link DUB-E100 USB2.0 to Fast Ethernet Adapter"
                    CoInstallers:"Not Available"
                    Default IP Gateway:"Not Available"
                    DHCP Enabled:"Yes"
                    DHCP Lease Expires:"12.02.2019 09:29"
                    DHCP Lease Obtained:"12.02.2019 09:29"
                    DHCP Server:"255.255.255.255"
                    Driver:"DKE100.sys"
                    Driver Date:"11.17.2015 12:00"
                    Driver Path:"C:\Windows\system32\drivers\DKE100.sys"
                    Driver Provider:"D-Link"
                    Driver Version:"3.16.10.0"
                    Index:"0017"
                    INF:"oem115.inf"
                    INF Section:"DKE100.Ndi"
                    Install Date:"Not Available"
                    Installed:"Yes"
                    IP Address:"169.254.164.151;fe80::35:3f5f:7640:a497;fd53:7cb8:383:900::111"
                    IP Subnet:"255.255.0.0;64;64"
                    Last Error Code:"Not Available"
                    Last Error Code Description:"Not Available"
                    Last Reset:"12.02.2019 09:29"
                    Location:"Port_#0001.Hub_#0009"
                    MAC Address:"C4:A8:1D:6D:CD:B0"
                    Manufacturer:"D-Link"
                    Media Type:"Unknown"
                    Net Connection ID:"USBEthDLink"
                    NetCfgInstanceId:"{D73EB97B-6B4F-4D24-B7D0-A932EEAC91B7}"
                    Number of VLANs:"0"
                    PNP Device ID:"USB\VID_2001&PID_1A02\6DCDB0"
                    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:"D-Link DUB-E100 USB2.0 to Fast Ethernet Adapter"
                    Service Name:"DKE100"
                    Status:"Link Up - This device is not linked at its maximum capable speed"
                    Team Name:"Not in a team"
                    Temperature:"Not Supported"
                    Type:"Ethernet 802.3"
                    - "Service Bindings"
                         Client for Microsoft Networks:
                         File and Printer Sharing for Microsoft Networks:
                         Internet Protocol Version 4 (TCP/IPv4):
                         Internet Protocol Version 6 (TCP/IPv6):
                         Juniper Network Service:
                         Link-Layer Topology Discovery Mapper I/O Driver:
                         Link-Layer Topology Discovery Responder:
                         Microsoft LLDP Protocol Driver:
                         Npcap Packet Driver (NPCAP):
                         Npcap Packet Driver (NPCAP) (Wi-Fi):
                         Npcap Packet Driver (NPF):
                         Npcap Packet Driver (NPF) (Wi-Fi):
                         QoS Packet Scheduler:
                         VirtualBox NDIS6 Bridged Networking Driver:
                    - "Settings"
                         *DeviceSleepOnDisconnect:Device sleep on disconnect:"Enabled (1)"
                         *FlowControl:Flow Control:"Rx & Tx Enabled (3)"
                         *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)"
                         *PMARPOffload:ARP Offload:"Enabled (1)"
                         *PMNSOffload:NS Offload:"Enabled (1)"
                         *PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enabled (3)"
                         *SelectiveSuspend:SelectiveSuspend:"Disabled (0)"
                         *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)"
                         *SSIdleTimeout:SSIdleTimeout:"5 (5)"
                         *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)"
                         *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)"
                         *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)"
                         *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)"
                         *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)"
                         *WakeOnPattern:Wake on pattern match:"Enabled (1)"
                         AutoDetach:AutoDetach:"Disabled (0)"
                         MaskTimer:Mask WakeUp Event Timer:"4 seconds (1)"
                         VLAN_ID:VLAN ID:"2304 (2304)"
                         WolLinkSpeed:WOL Link Speed:"Use EEPROM Setting (1)"
               - "Intel(R) Dual Band Wireless-AC 8260"
                    Access Point:
                    Authentication:
                    Availability:"Running or Full Power"
                    - "Caption":"Intel(R) Dual Band Wireless-AC 8260"
                         Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Dual+Band+Wireless+AC+8260"
                    Channel:
                    Cipher:
                    CoInstallers:"Not Available"
                    Connection Mode:
                    Default IP Gateway:"Not Available"
                    DHCP Enabled:"Yes"
                    DHCP Lease Expires:"Not Available"
                    DHCP Lease Obtained:"Not Available"
                    DHCP Server:"Not Available"
                    Driver:"Netwtw06.sys"
                    Driver Date:"08.26.2019 12:00"
                    Driver Path:"C:\Windows\system32\drivers\Netwtw06.sys"
                    Driver Provider:"Intel"
                    Driver Version:"20.70.12.5"
                    Index:"0001"
                    INF:"oem173.inf"
                    INF Section:"Install_MPCIEX_MidSARM2AENBT_8260_AC_2x2_HMC_WINT_64_AC"
                    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:"12.02.2019 09:29"
                    Location:"PCI bus 4, device 0, function 0"
                    MAC Address:"E4:B3:18:89:D8:6B"
                    Manufacturer:"Intel Corporation"
                    Media Type:
                    Net Connection ID:"Wi-Fi"
                    NetCfgInstanceId:"{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0}"
                    Network Name:"Wi-Fi"
                    Network Type:
                    Number of VLANs:"0"
                    PNP Device ID:"PCI\VEN_8086&DEV_24F3&SUBSYS_01308086&REV_3A\4&334743A6&0&00E2"
                    Port:"Not Available"
                    Power Management (Low Power):"Not Available"
                    Power Management (Wake On LAN):"Not Available"
                    Power Management (Wake on Magic Packet):"Not Available"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Product Type:"Intel(R) Dual Band Wireless-AC 8260"
                    Profile:
                    Radio Type:
                    Receive Rate:
                    Service Name:"Netwtw06"
                    Signal Strength:
                    State:"disconnected"
                    Status:"Enabled"
                    Team Name:"Not in a team"
                    Temperature:
                    Transmit Rate:
                    Type:"Ethernet 802.3"
                    - "Service Bindings"
                         Client for Microsoft Networks:
                         File and Printer Sharing for Microsoft Networks:
                         Internet Protocol Version 4 (TCP/IPv4):
                         Internet Protocol Version 6 (TCP/IPv6):
                         Juniper Network Service:
                         Link-Layer Topology Discovery Mapper I/O Driver:
                         Link-Layer Topology Discovery Responder:
                         Microsoft LLDP Protocol Driver:
                         Npcap Packet Driver (NPCAP):
                         Npcap Packet Driver (NPCAP) (Wi-Fi):
                         Npcap Packet Driver (NPF):
                         Npcap Packet Driver (NPF) (Wi-Fi):
                         QoS Packet Scheduler:
                         VirtualBox NDIS6 Bridged Networking Driver:
                    - "Settings"
                         *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)"
                         *PacketCoalescing:Packet Coalescing:"Enabled (1)"
                         *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)"
                         *PMNSOffload:NS offload for WoWLAN:"Enabled (1)"
                         *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)"
                         *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)"
                         *WakeOnPattern:Wake on Pattern Match:"Enabled (1)"
                         ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)"
                         ChannelWidth52:Channel Width for 5GHz:"Auto (1)"
                         CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)"
                         FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)"
                         IbssTxPower:Transmit Power:"5. Highest (100)"
                         IEEE11nMode:802.11n/ac Wireless Mode:"802.11ac (2)"
                         MIMOPowerSaveMode:MIMO Power Save Mode:"Auto SMPS (0)"
                         RoamAggressiveness:Roaming Aggressiveness:"3. Medium (2)"
                         RoamingPreferredBandType:Preferred Band:"1. No Preference (0)"
                         ThroughputBoosterEnabled:Throughput Booster:"Disabled (0)"
                         uAPSDSupport:U-APSD support:"Disabled (0)"
                         WirelessMode:802.11a/b/g Wireless Mode:"6. Dual Band 802.11a/b/g (34)"
               - "Intel(R) Ethernet Connection (2) I219-LM"
                    Availability:"Running or Full Power"
                    - "Caption":"Intel(R) Ethernet Connection (2) I219-LM"
                         Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Ethernet+Connection+(2)+I219+LM"
                    CoInstallers:"Not Available"
                    Default IP Gateway:"10.9.20.1"
                    DHCP Enabled:"Yes"
                    DHCP Lease Expires:"12.12.2019 11:02"
                    DHCP Lease Obtained:"12.05.2019 09:08"
                    DHCP Server:"10.5.139.200"
                    Driver:"e1d65x64.sys"
                    Driver Date:"05.09.2019 12:00"
                    Driver Path:"C:\Windows\system32\DriverStore\FileRepository\e1d65x64.inf_amd64_b990b1f51e1e15f0\e1d65x64.sys"
                    Driver Provider:"Intel"
                    Driver Version:"12.18.9.11"
                    ETrackID:"0x00000000"
                    Index:"0003"
                    INF:"oem181.inf"
                    INF Section:"E15B7.10.0.1"
                    Install Date:"Not Available"
                    Installed:"Yes"
                    IP Address:"10.9.20.121;fe80::898a:6179:c348:c274"
                    IP Subnet:"255.255.255.0;64"
                    Last Error Code:"Not Available"
                    Last Error Code Description:"Not Available"
                    Last Reset:"12.02.2019 09:29"
                    Location:"PCI bus 0, device 31, function 6"
                    MAC Address:"C8:5B:76:28:07:23"
                    Manufacturer:"Intel"
                    Media Type:"Copper"
                    Net Connection ID:"Ethernet 6"
                    NetCfgInstanceId:"{A1B6165C-CBFE-4475-9177-8665B22FBA13}"
                    Number of VLANs:"0"
                    NVM Version:"0x00000000"
                    Part Number:"1000FF-0FF"
                    PNP Device ID:"PCI\VEN_8086&DEV_15B7&SUBSYS_223317AA&REV_31\3&B1BFB68&0&FE"
                    Port:"Not Available"
                    Power Management (Low Power):"Not Available"
                    Power Management (Wake On LAN):"Not Available"
                    Power Management (Wake on Magic Packet):"Not Available"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Product Type:"Intel(R) Ethernet Connection (2) I219-LM"
                    Service Name:"e1dexpress"
                    Status:"Link Up"
                    Team Name:"Not in a team"
                    Temperature:"Not Supported"
                    Type:"Ethernet 802.3"
                    - "Service Bindings"
                         Client for Microsoft Networks:
                         File and Printer Sharing for Microsoft Networks:
                         Internet Protocol Version 4 (TCP/IPv4):
                         Internet Protocol Version 6 (TCP/IPv6):
                         Juniper Network Service:
                         Link-Layer Topology Discovery Mapper I/O Driver:
                         Link-Layer Topology Discovery Responder:
                         Microsoft LLDP Protocol Driver:
                         Npcap Packet Driver (NPCAP):
                         Npcap Packet Driver (NPCAP) (Wi-Fi):
                         Npcap Packet Driver (NPF):
                         Npcap Packet Driver (NPF) (Wi-Fi):
                         QoS Packet Scheduler:
                         VirtualBox NDIS6 Bridged Networking Driver:
                    - "Settings"
                         *FlowControl:Flow Control:"Rx & Tx Enabled (3)"
                         *InterruptModeration:Interrupt Moderation:"Enabled (1)"
                         *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)"
                         *JumboPacket:Jumbo Packet:"Disabled (1514)"
                         *LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)"
                         *LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)"
                         *NumRssQueues:Maximum Number of RSS Queues:"2 Queues (2)"
                         *PMARPOffload:Protocol ARP Offload:"Enabled (1)"
                         *PMNSOffload:Protocol NS Offload:"Enabled (1)"
                         *PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enabled (3)"
                         *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 6 (Ethernet 6)"
                         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:"Enabled (1)"
                         SipsEnabled:System Idle Power Saver:"Disabled (0)"
                         ULPMode:Ultra Low Power Mode:"Enabled (1)"
                         WaitAutoNegComplete:Wait for Link:"Auto Detect (2)"
                         WakeOnLink:Wake on Link Settings:"Disabled (0)"
               - "Npcap Loopback Adapter"
                    Availability:"Running or Full Power"
                    Caption:"Npcap Loopback Adapter"
                    CoInstallers:"Not Available"
                    Default IP Gateway:"Not Available"
                    DHCP Enabled:"Yes"
                    DHCP Lease Expires:"12.02.2019 09:29"
                    DHCP Lease Obtained:"12.02.2019 09:29"
                    DHCP Server:"255.255.255.255"
                    Driver:"loop.sys"
                    Driver Date:"06.21.2006 12:00"
                    Driver Path:"C:\Windows\system32\drivers\loop.sys"
                    Driver Provider:"Microsoft"
                    Driver Version:"10.0.17134.1"
                    Index:"0034"
                    INF:"netloop.inf"
                    INF Section:"kmloop.ndi.NT"
                    Install Date:"Not Available"
                    Installed:"Yes"
                    IP Address:"169.254.202.101;fe80::d5c2:7b8a:7c36:ca65"
                    IP Subnet:"255.255.0.0;64"
                    Last Error Code:"Not Available"
                    Last Error Code Description:"Not Available"
                    Last Reset:"12.02.2019 09:29"
                    Location:"Not Available"
                    MAC Address:"02:00:4C:4F:4F:50"
                    Manufacturer:"Microsoft"
                    Media Type:
                    Net Connection ID:"Npcap Loopback Adapter"
                    NetCfgInstanceId:"{64A973EE-9100-47B8-BAD9-8B1C5BE8A771}"
                    Number of VLANs:"0"
                    PNP Device ID:"ROOT\NET\0000"
                    Port:"Not Available"
                    Power Management (Low Power):"Not Available"
                    Power Management (Wake On LAN):"Not Available"
                    Power Management (Wake on Magic Packet):"Not Available"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Product Type:"Microsoft KM-TEST Loopback Adapter"
                    Service Name:"kmloop"
                    Status:"Enabled"
                    Team Name:"Not in a team"
                    Temperature:
                    Type:"Ethernet 802.3"
                    - "Service Bindings"
                         Client for Microsoft Networks:
                         File and Printer Sharing for Microsoft Networks:
                         Internet Protocol Version 4 (TCP/IPv4):
                         Internet Protocol Version 6 (TCP/IPv6):
                         Juniper Network Service:
                         Link-Layer Topology Discovery Mapper I/O Driver:
                         Link-Layer Topology Discovery Responder:
                         Microsoft LLDP Protocol Driver:
                         Npcap Packet Driver (NPCAP):
                         Npcap Packet Driver (NPCAP) (Wi-Fi):
                         Npcap Packet Driver (NPF):
                         Npcap Packet Driver (NPF) (Wi-Fi):
                         QoS Packet Scheduler:
                         VirtualBox NDIS6 Bridged Networking Driver:
                    - "Settings"
                         NetworkAddress:Network Address:
               - "TAP-Windows Adapter V9"
                    Availability:"Running or Full Power"
                    Caption:"TAP-Windows Adapter V9"
                    CoInstallers:"Not Available"
                    Default IP Gateway:"Not Available"
                    DHCP Enabled:"No"
                    DHCP Lease Expires:"Not Available"
                    DHCP Lease Obtained:"Not Available"
                    DHCP Server:"Not Available"
                    Driver:"tap0901.sys"
                    Driver Date:"02.07.2012 12:00"
                    Driver Path:"C:\Windows\system32\drivers\tap0901.sys"
                    Driver Provider:"TAP-Windows Provider V9"
                    Driver Version:"9.0.0.9"
                    Index:"0025"
                    INF:"oem148.inf"
                    INF Section:"tap0901.ndi"
                    Install Date:"Not Available"
                    Installed:"Yes"
                    IP Address:"Not Available"
                    IP Subnet:"Not Available"
                    Last Error Code:"Not Available"
                    Last Error Code Description:"Not Available"
                    Last Reset:"12.02.2019 09:29"
                    Location:"Not Available"
                    MAC Address:"Not Available"
                    Manufacturer:"TAP-Windows Provider V9"
                    Media Type:
                    Net Connection ID:"icas_sdk_tap0"
                    NetCfgInstanceId:"{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0}"
                    Number of VLANs:"0"
                    PNP Device ID:"ROOT\NET\0001"
                    Port:"Not Available"
                    Power Management (Low Power):"Not Available"
                    Power Management (Wake On LAN):"Not Available"
                    Power Management (Wake on Magic Packet):"Not Available"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Product Type:"TAP-Windows Adapter V9"
                    Service Name:"tap0901"
                    Status:"Device is disabled."
                    Team Name:"Not in a team"
                    Temperature:
                    Type:"Not Available"
                    - "Service Bindings"
                         Client for Microsoft Networks:
                         File and Printer Sharing for Microsoft Networks:
                         Internet Protocol Version 4 (TCP/IPv4):
                         Internet Protocol Version 6 (TCP/IPv6):
                         Juniper Network Service:
                         Link-Layer Topology Discovery Mapper I/O Driver:
                         Link-Layer Topology Discovery Responder:
                         Microsoft LLDP Protocol Driver:
                         Npcap Packet Driver (NPCAP):
                         Npcap Packet Driver (NPCAP) (Wi-Fi):
                         Npcap Packet Driver (NPF):
                         Npcap Packet Driver (NPF) (Wi-Fi):
                         QoS Packet Scheduler:
                         VirtualBox NDIS6 Bridged Networking Driver:
                    - "Settings"
                         AllowNonAdmin:Non-Admin Access:"Allowed (1)"
                         MediaStatus:Media Status:"Always Connected (1)"
                         MTU:MTU:"1500 (1500)"
               - "VirtualBox Host-Only Ethernet Adapter"
                    Availability:"Running or Full Power"
                    Caption:"VirtualBox Host-Only Ethernet Adapter"
                    CoInstallers:"Not Available"
                    Default IP Gateway:"Not Available"
                    DHCP Enabled:"No"
                    DHCP Lease Expires:"Not Available"
                    DHCP Lease Obtained:"Not Available"
                    DHCP Server:"Not Available"
                    Driver:"VBoxNetAdp6.sys"
                    Driver Date:"10.10.2019 12:00"
                    Driver Path:"C:\Windows\system32\DRIVERS\VBoxNetAdp6.sys"
                    Driver Provider:"Oracle Corporation"
                    Driver Version:"6.0.14.0"
                    Index:"0029"
                    INF:"oem90.inf"
                    INF Section:"VBoxNetAdp6.ndi"
                    Install Date:"Not Available"
                    Installed:"Yes"
                    IP Address:"192.168.56.1;fe80::4cd4:351d:2c42:2159"
                    IP Subnet:"255.255.255.0;64"
                    Last Error Code:"Not Available"
                    Last Error Code Description:"Not Available"
                    Last Reset:"12.02.2019 09:29"
                    Location:"Not Available"
                    MAC Address:"0A:00:27:00:00:06"
                    Manufacturer:"Oracle Corporation"
                    Media Type:
                    Net Connection ID:"Ethernet 9"
                    NetCfgInstanceId:"{0BAF35C1-225D-46F1-A88D-B7BB04994AC3}"
                    Number of VLANs:"0"
                    PNP Device ID:"ROOT\NET\0002"
                    Port:"Not Available"
                    Power Management (Low Power):"Not Available"
                    Power Management (Wake On LAN):"Not Available"
                    Power Management (Wake on Magic Packet):"Not Available"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Product Type:"VirtualBox Host-Only Ethernet Adapter"
                    Service Name:"VBoxNetAdp"
                    Status:"Enabled"
                    Team Name:"Not in a team"
                    Temperature:
                    Type:"Ethernet 802.3"
                    - "Service Bindings"
                         Client for Microsoft Networks:
                         File and Printer Sharing for Microsoft Networks:
                         Internet Protocol Version 4 (TCP/IPv4):
                         Internet Protocol Version 6 (TCP/IPv6):
                         Juniper Network Service:
                         Link-Layer Topology Discovery Mapper I/O Driver:
                         Link-Layer Topology Discovery Responder:
                         Microsoft LLDP Protocol Driver:
                         Npcap Packet Driver (NPCAP):
                         Npcap Packet Driver (NPCAP) (Wi-Fi):
                         Npcap Packet Driver (NPF):
                         Npcap Packet Driver (NPF) (Wi-Fi):
                         QoS Packet Scheduler:
                         VirtualBox NDIS6 Bridged Networking Driver:
          - "Operating System"
               .Net Framework Version:"2.0,3.0,3.5,4.0,4.7"
               Boot Device:"\Device\HarddiskVolume1"
               Internet Browser:"Internet Explorer,11.1130"
               Locale:"United States"
               OS Manufacturer:"Microsoft Corporation"
               OS Name:"Microsoft Windows 10 Enterprise"
               Other OS Description:"Not Available"
               Page File:"C:\pagefile.sys"
               Page File Space:"0,98 GB"
               Physical Memory (Available):"18,61 GB"
               Physical Memory (Installed):"32 GB"
               Physical Memory (Total):"31,38 GB"
               System Directory:"C:\Windows\system32"
               Version:"10.0.17134 Build 17134"
               Virtual Memory (Available):"18,26 GB"
               Virtual Memory (Total):"32,36 GB"
               Windows Directory:"C:\Windows"
               - "Installed Updates"
                    KB2151757:"Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219 [17.06.2019]"
                    KB2151757:"Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219 [17.06.2019]"
                    KB2467173:"Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219 [17.06.2019]"
                    KB2467173:"Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219 [17.06.2019]"
                    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 [01.10.2019]"
                    KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB4287903:"Security Update [6/19/2018]"
                    KB4346084:"Update [8/9/2019]"
                    KB4497398:"Security Update [6/17/2019]"
                    KB4509094:"Security Update [9/9/2019]"
                    KB4512576:"Security Update [10/1/2019]"
                    KB4516115:"Security Update [10/1/2019]"
                    KB4521861:"Security Update [10/25/2019]"
                    KB4523203:"Security Update [11/27/2019]"
                    KB4525237:"Security Update [11/28/2019]"
                    KB982573:"Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219 [17.06.2019]"
                    KB982573:"Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219 [17.06.2019]"
                    SP1:"Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219 [Not Available]"
                    SP1:"Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219 [Not Available]"
          - "Processor"
               - "Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz"
                    Architecture:"x64"
                    ATPO:"Not Available"
                    Availability:"Running or Full Power"
                    Caption:"Intel64 Family 6 Model 94 Stepping 3"
                    - "Chipset Name":"Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz"
                         Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i7+6820HQ+CPU+"
                    CPU Speed:"2,712 GHz"
                    Current Voltage:"1.6 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:"Intel Core™ i7-2760QM"
                    FPO:"Not Available"
                    INF:"cpu.inf"
                    INF Section:"IntelPPM_Inst.NT"
                    Install Date:"Not Available"
                    Last Error Code:"Not Available"
                    Level 1 Cache:"4 x 128 KB"
                    Level 2 Cache:"4 x 1024 KB"
                    Level 3 Cache:"8 MB"
                    Load:"7%"
                    Manufacturer:"GenuineIntel"
                    Model:"94"
                    Name:"Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz"
                    Number of Cores:"4"
                    Number of Cores Enabled:"4"
                    Number of Logical Processors:"8"
                    Part Number:"None"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Processor ID:"BFEBFBFF000506E3"
                    Revision:"24067"
                    Serial Number:"None"
                    Service Name:"intelppm"
                    Status:"OK"
                    Stepping:"3"
                    Version:"Not Available"
          - "Storage"
               - "HGST HTS541010A7E630"
                    Capablities:"Random Access, Supports Writing, SMART Notification"
                    Caption:"HGST HTS541010A7E630"
                    Cylinder - Total:"121601"
                    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:"SE0ZCA10"
                    Heads - Total:"255"
                    Index:"1"
                    INF:"disk.inf"
                    Install Date:"Not Available"
                    Interface Type:"IDE"
                    Manufacturer:"(Standard disk drives)"
                    Model:"HGST HTS541010A7E630"
                    Name:"\\.\PHYSICALDRIVE1"
                    Partitions:"1"
                    Physical Sector Size:"4096"
                    PNP Device ID:"SCSI\DISK&VEN_HGST&PROD_HTS541010A7E630\4&31CE16B3&0&000300"
                    Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available"
                    Sectors - Per Track:"63"
                    Sectors - Total:"1953520065"
                    Serial Number:"S0A001SSJ35LGK"
                    Size:"931,51 GB"
                    Size – Available:"37,20 GB"
                    SMART Attributes:"Self-Test: 224 minutes, OK, Short Self-Test: 2 minutes, OK"
                    Status:"OK"
                    Tracks - Per Cylinder:"255"
                    Tracks - Total:"31008255"
                    - "D:"
                         Availability:"Not Available"
                         Caption:"D:"
                         Compression Method:"Not Compressed"
                         Description:"Local Fixed Disk"
                         File System:"NTFS"
                         Name:"Not Available"
                         Serial Number:"6E571F08"
                         Size:"931,510738372803 GB"
                         Size – Available:"37,2032241821289 GB"
                         Status:"Not Available"
                         Volume Dirty:"No"
                    - "SMART"
                         0x01  Raw Read Error Rate:0:"0"
                         0x02  Throughput Performance:0:"50"
                         0x03  Spin Up Time:64424509441:"50"
                         0x04  Start/Stop Count:4846:"0"
                         0x05  Reallocated Sector Count:0:"50"
                         0x07  Seek Error Rate:0:"50"
                         0x08  Seek Timer Performance:0:"50"
                         0x09  Power-On Hours:3542:"0"
                         0x0A  Spin Retry Count:0:"50"
                         0x0C  Power Cycle Count:1567:"0"
                         0xBF  G-sense Rate/Servo Tracking:0:"0"
                         0xC0  Unsafe Shutdown Count:31:"0"
                         0xC1  Load/Unload Cycle Count:34582:"0"
                         0xC2  Internal Device Temperature:33° C:"0"
                         0xC4  Reallocation Count:0:"0"
                         0xC5  Current Pending Errors Count:0:"0"
                         0xC6  Uncorrectable Sector Count:0:"0"
                         0xC7  CRC Error Count:0:"0"
                         0xDF  Load/Unload Retry Count:0:"0"
               - "Microsoft Virtual Disk"
                    Capablities:"Random Access, Supports Writing"
                    Caption:"Microsoft Virtual Disk"
                    Cylinder - Total:"5221"
                    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.0"
                    Heads - Total:"255"
                    Index:"2"
                    INF:"disk.inf"
                    Install Date:"Not Available"
                    Interface Type:"SCSI"
                    Manufacturer:"(Standard disk drives)"
                    Model:"Microsoft Virtual Disk"
                    Name:"\\.\PHYSICALDRIVE2"
                    Partitions:"1"
                    PNP Device ID:"SCSI\DISK&VEN_MSFT&PROD_VIRTUAL_DISK\2&1F4ADFFE&0&000001"
                    Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available"
                    SCSI Bus:"0"
                    SCSI LUN:"1"
                    SCSI Port:"3"
                    Sectors - Per Track:"63"
                    Sectors - Total:"83875365"
                    Serial Number:"Not Available"
                    Size:"39,99 GB"
                    Size – Available:"0.0 bytes"
                    Status:"OK"
                    Tracks - Per Cylinder:"255"
                    Tracks - Total:"1331355"
               - "TOSHIBA THNSFJ256GDNU A"
                    Capablities:"Random Access, Supports Writing, SMART Notification"
                    Caption:"TOSHIBA THNSFJ256GDNU A"
                    Cylinder - Total:"31130"
                    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:"JYLA1102"
                    Heads - Total:"255"
                    Index:"0"
                    INF:"disk.inf"
                    Install Date:"Not Available"
                    Interface Type:"IDE"
                    Manufacturer:"(Standard disk drives)"
                    Model:"TOSHIBA THNSFJ256GDNU A"
                    Name:"\\.\PHYSICALDRIVE0"
                    Partitions:"2"
                    Physical Sector Size:"512"
                    PNP Device ID:"SCSI\DISK&VEN_TOSHIBA&PROD_THNSFJ256GDNU\4&31CE16B3&0&000000"
                    Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available"
                    Sectors - Per Track:"63"
                    Sectors - Total:"500103450"
                    Serial Number:"66BS108OTJ4V"
                    Size:"238,47 GB"
                    Size – Available:"56,09 GB"
                    SMART Attributes:"Self-Test: 10 minutes, OK, Short Self-Test: 2 minutes, OK"
                    Status:"OK"
                    Tracks - Per Cylinder:"255"
                    Tracks - Total:"7938150"
                    - "C:"
                         Availability:"Not Available"
                         Caption:"C:"
                         Compression Method:"Not Compressed"
                         Description:"Local Fixed Disk"
                         File System:"NTFS"
                         Name:"Not Available"
                         Serial Number:"56556101"
                         Size:"238,130855560303 GB"
                         Size – Available:"56,0852165222168 GB"
                         Status:"Not Available"
                         Volume Dirty:"No"
                    - "SMART"
                         0x01  Raw Read Error Rate:0:"0"
                         0x02  Throughput Performance:0:"50"
                         0x03  Spin Up Time:0:"50"
                         0x05  Reallocated Sector Count:0:"50"
                         0x07  Seek Error Rate:0:"50"
                         0x08  Seek Timer Performance:0:"50"
                         0x09  Power-On Hours:3659:"0"
                         0x0A  Spin Retry Count:0:"50"
                         0x0C  Power Cycle Count:1568:"0"
                         0xAA  Available Reserved Space:0:"10"
                         0xAD  Wear Leveling Count:0:"0"
                         0xAF  Power Loss Protection Failure:0:"10"
                         0xB4  Unused Reserved Block Count Total:100:"10"
                         0xBB  Uncorrectable Error Count:0:"0"
                         0xC0  Unsafe Shutdown Count:114:"0"
                         0xC2  Internal Device Temperature:40° C:"0"
                         0xC5  Current Pending Errors Count:0:"0"
                         0xC7  CRC Error Count:0:"0"
                         0xE9  Media Wearout Indicator:0:"1"
                         0xF0  Head Flying Hours:0:"50"
                         0xF1  Total LBAs Written:5431:"0"
                         0xF2  Total LBAs Read:3958:"0"
                         0xF9  Total NAND Writes:16918:"0"
...#SSU#...
#Logs#System Messages#Included
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Npcap Packet Driver (NPF) (Wi-Fi) service failed to start due to the following error: 
The system cannot find the file specified.
-------------------------------------------------------------------
The Npcap Packet Driver (NPCAP) (Wi-Fi) service failed to start due to the following error: 
The system cannot find the file specified.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffffd08e45c0ce7c). A dump was saved in: C:\Windows\Minidump\120219-11843-01.dmp. Report Id: bc4a05b3-6c87-4d6a-865b-4a2c2f4b46cc.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The previous system shutdown at 10:24:03 on ‎02.‎12.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffff85016d988e7c). A dump was saved in: C:\Windows\Minidump\120119-9656-01.dmp. Report Id: 820c6686-e5dd-42aa-844b-79250a9b4288.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The previous system shutdown at 01:02:28 on ‎01.‎12.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The McAfee Agent Backwards Compatibility Service service failed to start due to the following error: 
The system cannot find the file specified.
-------------------------------------------------------------------
The McAfee Agent Common Services service failed to start due to the following error: 
The system cannot find the file specified.
-------------------------------------------------------------------
The McAfee Agent Service service failed to start due to the following error: 
The system cannot find the file specified.
-------------------------------------------------------------------
The McAfee Agent Backwards Compatibility Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.
-------------------------------------------------------------------
The McAfee Agent Common Services service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.
-------------------------------------------------------------------
The McAfee Agent Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID 
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID 
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffffc78569ed09ec). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c4281a60-5766-4993-9f9a-4b0f59e2d4df.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The RasMan service depends on the SstpSvc service which failed to start because of the following error: 
The operation completed successfully.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The previous system shutdown at 11:29:11 on ‎19.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
The Npcap Packet Driver (NPCAP) (Wi-Fi) service failed to start due to the following error: 
The system cannot find the file specified.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The previous system shutdown at 11:16:36 on ‎19.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
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.elektrobit.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.elektrobit.com. The TLS connection request has failed. The attached data contains the server certificate.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffff810ea9da4e7c). A dump was saved in: C:\Windows\Minidump\111919-15656-01.dmp. Report Id: 9854088c-4107-4ed2-8cf5-1fe4c58a0c4e.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 11:10:30 on ‎19.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffffd08561ef0c1c). A dump was saved in: C:\Windows\Minidump\111819-16515-01.dmp. Report Id: 5883fc8e-0ebc-4c42-ba27-a1ee3aef5938.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Bootmgr failed to obtain the BitLocker volume master key from the TPM.
-------------------------------------------------------------------
Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match.
-------------------------------------------------------------------
Bootmgr failed to unseal VMK using the TPM
-------------------------------------------------------------------
The previous system shutdown at 19:42:48 on ‎18.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service BITS with arguments "Unavailable" in order to run the server:
{4991D34B-80A1-4291-83B6-3328366B9097}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server:
{9E175B6D-F52A-11D8-B9A5-505054503030}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The NlaSvc service depends on the Dhcp service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The mrxsmb10 service depends on the mrxsmb service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The IKEEXT service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The Netlogon service depends on the LanmanWorkstation service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The mrxsmb20 service depends on the mrxsmb service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The mrxsmb service depends on the rdbss service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The Wcmsvc service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The Dnscache service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The nsi service depends on the nsiproxy service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The Dhcp service depends on the AFD service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
Bootmgr failed to obtain the BitLocker volume master key from the TPM.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffff808e8d57d9ec). A dump was saved in: C:\Windows\Minidump\111819-16046-01.dmp. Report Id: 93e1d863-967c-49bf-b933-8e2a25b2615f.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 17:43:19 on ‎18.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffff9b8bc6fa9e7c). A dump was saved in: C:\Windows\Minidump\111819-15796-01.dmp. Report Id: 48436e93-4c9e-4829-85f7-99336853c8b7.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 17:28:58 on ‎18.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffff8d06d38f09ec). A dump was saved in: C:\Windows\Minidump\111819-15953-01.dmp. Report Id: 1d7965a3-f520-4eea-a24f-81c19199f61c.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Bootmgr failed to obtain the BitLocker volume master key from the TPM.
-------------------------------------------------------------------
Bootmgr failed to obtain the BitLocker volume master key from the TPM because the PCRs did not match.
-------------------------------------------------------------------
Bootmgr failed to unseal VMK using the TPM
-------------------------------------------------------------------
The previous system shutdown at 16:37:26 on ‎18.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffffba8a23c58e7c). A dump was saved in: C:\Windows\Minidump\111819-16328-01.dmp. Report Id: a01508ea-e115-46d5-91f8-ebccaed41c07.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 15:42:12 on ‎18.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffffe10ddeae39ec). A dump was saved in: C:\Windows\Minidump\111819-20687-01.dmp. Report Id: 0cd7baa1-6047-4949-b3a8-d821ec5a7152.
-------------------------------------------------------------------
The previous system shutdown at 15:19:58 on ‎18.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume9'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The system detected an address conflict for IP address 0.0.0.0 with the system having network hardware address 58-F3-9C-C8-0F-18. Network operations on this system may be disrupted as a result.
-------------------------------------------------------------------
Initialization failed because the transport refused to open initial addresses.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to bind to physical adapter. To resolve, remove the adapter team and then create a new team.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Unable to bind to physical adapter. To resolve, remove the adapter team and then create a new team.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
Unable to bind to physical adapter. To resolve, remove the adapter team and then create a new team.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3828592956-402884139-1670100498-1182904954-766661596-3240449192-2824924573). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
There was an error while attempting to read the local hosts file.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to bind to physical adapter. To resolve, remove the adapter team and then create a new team.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Unable to bind to physical adapter. To resolve, remove the adapter team and then create a new team.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
Initialization failed because the driver device could not be created. Use the string "C85B76280723" 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 "C85B76280723" 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 "C85B76280723" 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 "C85B76280723" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the  Globally Unique Interface Identifier (GUID) if NetBT was unable to  map from GUID to MAC address. If neither the MAC address nor the GUID were  available, the string represents a cluster device name. 
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server:
{9E175B6D-F52A-11D8-B9A5-505054503030}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The NlaSvc service depends on the Dhcp service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The mrxsmb10 service depends on the mrxsmb service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The IKEEXT service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The Netlogon service depends on the LanmanWorkstation service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The mrxsmb20 service depends on the mrxsmb service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The mrxsmb service depends on the rdbss service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The Wcmsvc service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The Dnscache service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The nsi service depends on the nsiproxy service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The Dhcp service depends on the AFD service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Crash dump initialization failed!
-------------------------------------------------------------------
Bootmgr failed to obtain the BitLocker volume master key from the TPM.
-------------------------------------------------------------------
The previous system shutdown at 14:40:12 on ‎06.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service MSIServer with arguments "" in order to run the server:
{000C101C-0000-0000-C000-000000000046}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server:
{9E175B6D-F52A-11D8-B9A5-505054503030}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server:
{9E175B6D-F52A-11D8-B9A5-505054503030}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}
-------------------------------------------------------------------
The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The IKEEXT service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The mrxsmb10 service depends on the mrxsmb service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The NlaSvc service depends on the Dhcp service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The Netlogon service depends on the LanmanWorkstation service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The mrxsmb20 service depends on the mrxsmb service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The mrxsmb service depends on the rdbss service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The Wcmsvc service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The Dnscache service depends on the nsi service which failed to start because of the following error: 
The dependency service or group failed to start.
-------------------------------------------------------------------
The nsi service depends on the nsiproxy service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The Dhcp service depends on the AFD service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Crash dump initialization failed!
-------------------------------------------------------------------
Bootmgr failed to obtain the BitLocker volume master key from the TPM.
-------------------------------------------------------------------
The previous system shutdown at 14:08:38 on ‎06.‎11.‎2019 was unexpected.
-------------------------------------------------------------------
Initialization failed because the driver device could not be created. Use the string "C85B76280723" 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 "C85B76280723" 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 processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Unable to bind to physical adapter. To resolve, remove the adapter team and then create a new team.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
Initialization failed because the driver device could not be created. Use the string "C85B76280723" 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 "C85B76280723" 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. 
-------------------------------------------------------------------
Unable to bind to physical adapter. To resolve, remove the adapter team and then create a new team.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{EBB3B0BD-AE2D-41EF-A915-6E61826A67A0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{0AD9EA51-3AD0-4103-A707-5AB05F9A88B0} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The server could not bind to the transport \Device\NetBT_Tcpip_{5337F70C-E335-4202-8D9F-69FF7761BD62} because another computer on the network has the same name.  The server could not start.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The system detected an address conflict for IP address 0.0.0.0 with the system having network hardware address 74-A2-E6-6D-81-19. Network operations on this system may be disrupted as a result.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x1000007e (0xffffffffc0000002, 0xfffff8006f760e48, 0xffff9d88ffbfad50, 0xffff9d88ffbfadf0). A dump was saved in: C:\Windows\Minidump\102719-10953-01.dmp. Report Id: 2e15a521-b8a1-434d-854c-62de588e6563.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 12:07:05 on ‎27.‎10.‎2019 was unexpected.
-------------------------------------------------------------------
Windows failed to resume from hibernate with error status 0xC0000001.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-369790889-758649975-2590125238-3182806329-1632673140-2312605162-3234368323). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The BITS service failed to start.  Error 0x8007045B.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-1733709577-1373043342-1118898707-1856316035-563121375-3188302324-909192184). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume7'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The utdrv service failed to start due to the following error: 
The system cannot find the file specified.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Miniport TAP-Windows Adapter V9 #2, {7B329C82-020B-4AFA-81DE-B4CDE5CDFA60}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Miniport TAP-Windows Adapter V9, {8DB7C1E7-FBAE-45EC-9F35-ABAF94F3B7FA}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
5007 - TX/CMD timeout (TfdQueue hanged)
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Miniport TAP-Windows Adapter V9 #3, {4910F005-ABF5-40E7-A6CC-A3D4D869B7E3}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Miniport TAP-Windows Adapter V9 #2, {5DB5CD0A-D1BF-4DE6-9804-4AC249764EF6}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Miniport TAP-Windows Adapter V9, {B62B3870-14A2-4967-A80E-2D448623BE78}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3455922341-2365479272-3858681413-4270629621-266949909-4232079924-3288879227). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3455922341-2365479272-3858681413-4270629621-266949909-4232079924-3288879227). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3455922341-2365479272-3858681413-4270629621-266949909-4232079924-3288879227). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3455922341-2365479272-3858681413-4270629621-266949909-4232079924-3288879227). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9E175B6D-F52A-11D8-B9A5-505054503030}
 and APPID 
{9E175B9C-F52A-11D8-B9A5-505054503030}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-3455922341-2365479272-3858681413-4270629621-266949909-4232079924-3288879227). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume4'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 16:34:54 on ‎02.‎10.‎2019 was unexpected.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 17:45:24 on ‎01.‎10.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
Windows.SecurityCenter.WscBrokerManager
 and APPID 
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
Windows.SecurityCenter.WscBrokerManager
 and APPID 
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 17:03:59 on ‎01.‎10.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The name "EBGROUP        :1d" could not be registered on the interface with IP address 10.9.22.96. The computer with the IP address 10.9.22.60 did not allow the name to be claimed by this computer.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
5007 - TX/CMD timeout (TfdQueue hanged)
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
5007 - TX/CMD timeout (TfdQueue hanged)
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the igfxCUIService2.0.0.0 service.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The System Update service terminated unexpectedly.  It has done this 1 time(s).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
5007 - TX/CMD timeout (TfdQueue hanged)
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
5007 - TX/CMD timeout (TfdQueue hanged)
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 10:36:04 on ‎21.‎09.‎2019 was unexpected.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Miniport Remote NDIS based Internet Sharing Device, {4D40FDEF-BA94-49CD-8FF6-797D1A8CFD86}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed)
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Mobile Broadband HL Service service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID 
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID 
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffffcb020b075e7c). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 48f119dc-b21c-4979-ae8e-0551a47d5d85.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 18:55:16 on ‎18.‎09.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000c2 (0x0000000000000004, 0x0000000000000000, 0x0000000000000000, 0xffffb58f553669ec). A dump was saved in: C:\Windows\Minidump\091819-12953-01.dmp. Report Id: c4f30c52-57ed-4cc9-8706-5304126a06a8.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 18:49:08 on ‎18.‎09.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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 (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Filter Manager failed to attach to volume '\Device\HarddiskVolume5'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.
-------------------------------------------------------------------
Metadata initial read: Primary metadata record on volume E: could not be found. Volume needs recovery.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID 
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID 
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
There was an error while attempting to read the local hosts file.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The system detected an address conflict for IP address 0.0.0.0 with the system having network hardware address 74-A2-E6-AB-E5-9A. Network operations on this system may be disrupted as a result.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID 
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
 and APPID 
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 and APPID 
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 12:54:31 on ‎23.‎08.‎2019 was unexpected.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one of more of the following: 
a) Name Resolution failure on the current domain controller. 
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
Windows.SecurityCenter.WscBrokerManager
 and APPID 
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
Windows.SecurityCenter.WscBrokerManager
 and APPID 
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
Windows.SecurityCenter.WscBrokerManager
 and APPID 
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The Group Policy Client service did not shut down properly after receiving a preshutdown control.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
Windows.SecurityCenter.WscBrokerManager
 and APPID 
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). 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 application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user EBGROUP\svlu2312 SID (S-1-5-21-1757981266-764733703-682003330-29427) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
Windows.SecurityCenter.WscBrokerManager
 and APPID 
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows attempted to read the file \\ebgroup.elektrobit.com\sysvol\ebgroup.elektrobit.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: 
a) Name Resolution/Network Connectivity to the current domain controller. 
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). 
c) The Distributed File System (DFS) client has been disabled.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Update Orchestrator Service service terminated with the following error: 
This operation returned because the timeout period expired.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The McAfee McShield service failed to start due to the following error: 
A system shutdown is in progress.
-------------------------------------------------------------------
The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server Microsoft.WindowsAlarms_10.1712.10611.0_x64__8wekyb3d8bbwe!App.AppXbmaqzcg8s38kj475pha2p493ghzamegd.mca did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {D63B10C5-BB46-4990-A94F-E40B9D520160} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wekyb3d8bbwe!MicrosoftEdge did not register with DCOM within the required timeout.
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy!App.AppXryc2qd338f5728r9gzzazav8206ba77s.mca as Unavailable/Unavailable. The error:
"298"
Happened while starting this command:
"C:\Windows\system32\backgroundTaskHost.exe" -ServerName:App.AppXmtcan0h2tfbfy7k9kn8hbxb6dmzz1zh0.mca
-------------------------------------------------------------------
The server Microsoft.Windows.ContentDeliveryManager_10.0.17134.1_neutral_neutral_cw5n1h2txyewy!App.AppX9s1cz53zc86xn39kwrb02jyft9ecn62r.mca did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {B9B05098-3E30-483F-87F7-027CA78DA287} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID 
Windows.SecurityCenter.WscBrokerManager
 and APPID 
Unavailable
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The Adobe Acrobat Update Service service terminated unexpectedly.  It has done this 3 time(s).
-------------------------------------------------------------------
The Adobe Acrobat Update Service service terminated unexpectedly.  It has done this 2 time(s).
-------------------------------------------------------------------
The Adobe Acrobat Update Service service terminated unexpectedly.  It has done this 1 time(s).
-------------------------------------------------------------------
The processing of Group Policy failed. Windows attempted to read the file \\ebgroup.elektrobit.com\sysvol\ebgroup.elektrobit.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: 
a) Name Resolution/Network Connectivity to the current domain controller. 
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). 
c) The Distributed File System (DFS) client has been disabled.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows attempted to read the file \\ebgroup.elektrobit.com\sysvol\ebgroup.elektrobit.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: 
a) Name Resolution/Network Connectivity to the current domain controller. 
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). 
c) The Distributed File System (DFS) client has been disabled.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain EBGROUP due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Printer Extensions and Notifications service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The application-specific permission settings do not grant Local Activation 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\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-------------------------------------------------------------------
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Dolby DAX2 API Service service terminated unexpectedly.  It has done this 1 time(s).
-------------------------------------------------------------------
The iphlpsvc service terminated with the following error: 
The device is not ready.
-------------------------------------------------------------------
The Spooler service terminated with the following error: 
Ran out of memory
...#SSU#...
#Logs#Direct-X Diagnostics#Included
------------------
System Information
------------------
      Time of this report: 12/5/2019, 21:16:10
             Machine name: ER03208N
               Machine Id: {3DD1E02C-FD20-47E4-871D-13CFDB106A52}
         Operating System: Windows 10 Enterprise 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804)
                 Language: German (Regional Setting: German)
      System Manufacturer: LENOVO
             System Model: 20EQS1KV00
                     BIOS: N1EET86W (v1.59 ) (type: BIOS)
                Processor: Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 CPUs), ~2.7GHz
                   Memory: 32768MB RAM
      Available OS Memory: 32134MB RAM
                Page File: 14501MB used, 18633MB available
              Windows Dir: C:\Windows
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 96 DPI (100 percent)
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Supported
           DxDiag Version: 10.00.17134.0001 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
      Display Tab 2: No problems found.
      Display Tab 3: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
           Card name: Intel(R) HD Graphics 530
        Manufacturer: Intel Corporation
           Chip type: Intel(R) HD Graphics Family
            DAC type: Internal
         Device Type: Full Device (POST)
          Device Key: Enum\PCI\VEN_8086&DEV_191B&SUBSYS_222E17AA&REV_06
       Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 
 Device Problem Code: No Problem
 Driver Problem Code: Unknown
      Display Memory: 16195 MB
    Dedicated Memory: 128 MB
       Shared Memory: 16067 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.580578,0.350109), Green(0.340344,0.560070), Blue(0.155773,0.125500), White Point(0.313977,0.329602)
   Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
        Monitor Name: Wide viewing angle & High density FlexView Display 1920x1080
       Monitor Model: unknown
          Monitor Id: LEN40BA
         Native Mode: 1920 x 1080(p) (60.020Hz)
         Output Type: Internal
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
      Advanced Color: Not Supported
         Driver Name: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd12umd64.dll
 Driver File Version: 26.20.0100.7106 (English)
      Driver Version: 26.20.100.7106
         DDI Version: 12
      Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 2.1
 Graphics Preemption: Triangle
  Compute Preemption: Thread
            Miracast: Supported
 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: 07.08.2019 01:00:00, 1832184 bytes
         WHQL Logo'd: Yes
     WHQL Date Stamp: Unknown
   Device Identifier: {D7B78E66-5A5B-11CF-D86F-4A02BDC2D735}
           Vendor ID: 0x8086
           Device ID: 0x191B
           SubSys ID: 0x222E17AA
         Revision ID: 0x0006
  Driver Strong Name: oem136.inf:5f63e5340a14bf6c:iSKLD_w10_DS:26.20.100.7106:pci\ven_8086&dev_191b&subsys_222e17aa
      Rank Of Driver: 00D10001
         Video Accel: 
         DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeMPEG2_IDCT  DXVA2_ModeVC1_D2010  DXVA2_ModeWMV9_IDCT  DXVA2_ModeVC1_IDCT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_Multiview_NoFGT  DXVA2_ModeHEVC_VLD_Main  DXVA2_ModeHEVC_VLD_Main10  
   Deinterlace Caps: {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YUY2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(UYVY,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(YV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(NV12,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {00000000-0000-0000-0000-000000000000}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
        D3D9 Overlay: 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: NVIDIA Quadro M1000M
        Manufacturer: NVIDIA
           Chip type: Quadro M1000M
            DAC type: Integrated RAMDAC
         Device Type: Full Device
          Device Key: Enum\PCI\VEN_10DE&DEV_13B1&SUBSYS_222E17AA&REV_A2
       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: 18075 MB
    Dedicated Memory: 2007 MB
       Shared Memory: 16067 MB
        Current Mode: 1920 x 1200 (32 bit) (59Hz)
         HDR Support: Not Supported
    Display Topology: Extend
 Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
     Color Primaries: Red(0.640148,0.330578), Green(0.300305,0.600109), Blue(0.150891,0.060070), White Point(0.313000,0.329602)
   Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
        Monitor Name: Generic PnP Monitor
       Monitor Model: SyncMaster
          Monitor Id: SAM0587
         Native Mode: 1920 x 1200(p) (59.950Hz)
         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\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll
 Driver File Version: 26.21.0014.3194 (English)
      Driver Version: 26.21.14.3194
         DDI Version: 12
      Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 2.4
 Graphics Preemption: DMA
  Compute Preemption: DMA
            Miracast: Not Supported by Graphics driver
 Hybrid Graphics GPU: Discrete
      Power P-states: Not Supported
      Virtualization: Paravirtualization 
          Block List: No Blocks
  Catalog Attributes: Universal:False Declarative:False 
   Driver Attributes: Final Retail
    Driver Date/Size: 19.09.2019 01:00:00, 959152 bytes
         WHQL Logo'd: Yes
     WHQL Date Stamp: Unknown
   Device Identifier: {D7B71E3E-50F1-11CF-6078-200218C2D735}
           Vendor ID: 0x10DE
           Device ID: 0x13B1
           SubSys ID: 0x222E17AA
         Revision ID: 0x00A2
  Driver Strong Name: oem175.inf:0f066de34da1cc29:Section066:26.21.14.3194:pci\ven_10de&dev_13b1&subsys_222e17aa
      Rank Of Driver: 00D10001
         Video Accel: 
         DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeVC1_D2010  DXVA2_ModeVC1_VLD  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeHEVC_VLD_Main  DXVA2_ModeMPEG4pt2_VLD_Simple  DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC  
   Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
        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: NVIDIA Quadro M1000M
        Manufacturer: NVIDIA
           Chip type: Quadro M1000M
            DAC type: Integrated RAMDAC
         Device Type: Full Device
          Device Key: Enum\PCI\VEN_10DE&DEV_13B1&SUBSYS_222E17AA&REV_A2
       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: 18075 MB
    Dedicated Memory: 2007 MB
       Shared Memory: 16067 MB
        Current Mode: 1920 x 1200 (32 bit) (59Hz)
         HDR Support: Not Supported
    Display Topology: Extend
 Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
     Color Primaries: Red(0.640148,0.330578), Green(0.300305,0.600109), Blue(0.150891,0.060070), White Point(0.313000,0.329602)
   Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
        Monitor Name: Generic PnP Monitor
       Monitor Model: SyncMaster
          Monitor Id: SAM0587
         Native Mode: 1920 x 1200(p) (59.950Hz)
         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\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll
 Driver File Version: 26.21.0014.3194 (English)
      Driver Version: 26.21.14.3194
         DDI Version: 12
      Feature Levels: 11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 2.4
 Graphics Preemption: DMA
  Compute Preemption: DMA
            Miracast: Not Supported by Graphics driver
 Hybrid Graphics GPU: Discrete
      Power P-states: Not Supported
      Virtualization: Paravirtualization 
          Block List: No Blocks
  Catalog Attributes: Universal:False Declarative:False 
   Driver Attributes: Final Retail
    Driver Date/Size: 19.09.2019 01:00:00, 959152 bytes
         WHQL Logo'd: Yes
     WHQL Date Stamp: Unknown
   Device Identifier: {D7B71E3E-50F1-11CF-6078-200218C2D735}
           Vendor ID: 0x10DE
           Device ID: 0x13B1
           SubSys ID: 0x222E17AA
         Revision ID: 0x00A2
  Driver Strong Name: oem175.inf:0f066de34da1cc29:Section066:26.21.14.3194:pci\ven_10de&dev_13b1&subsys_222e17aa
      Rank Of Driver: 00D10001
         Video Accel: 
         DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeVC1_D2010  DXVA2_ModeVC1_VLD  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeHEVC_VLD_Main  DXVA2_ModeMPEG4pt2_VLD_Simple  DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC  
   Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive 
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch 
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
        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 (3- USB PnP Audio Device)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: USB\VID_0C76&PID_161F&REV_0100&MI_00
        Manufacturer ID: 65535
             Product ID: 65535
                   Type: WDM
            Driver Name: USBAUDIO.sys
         Driver Version: 10.00.17134.0001 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 11.04.2018 00:00:00, 151552 bytes
            Other Files: 
        Driver Provider: Microsoft
         HW Accel Level: Basic
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

            Description: Speaker/HP (Realtek High Definition Audio)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0298&SUBSYS_17AA222E&REV_1001
        Manufacturer ID: 1
             Product ID: 100
                   Type: WDM
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.8777.0001 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 13.08.2019 00:00:00, 6964312 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 (3- USB PnP Audio Device)
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: USBAUDIO.sys
         Driver Version: 10.00.17134.0001 (English)
      Driver Attributes: Final Retail
          Date and Size: 4/12/2018 00:33:46, 151552 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF

            Description: Microphone Array (Realtek High Definition Audio)
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: RTKVHD64.sys
         Driver Version: 6.00.8777.0001 (English)
      Driver Attributes: Final Retail
          Date and Size: 8/20/2019 20:14:08, 6964312 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF

---------------------
Video Capture Devices
Number of Devices: 0
---------------------
-------------------
DirectInput Devices
-------------------
      Device Name: Mouse
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Keyboard
         Attached: 1
    Controller ID: n/a
Vendor/Product ID: n/a
        FF Driver: n/a

      Device Name: Microsoft� Comfort Mouse 4500
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x076C
        FF Driver: n/a

      Device Name: Apple Keyboard
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x05AC, 0x021E
        FF Driver: n/a

      Device Name: USB PnP Audio Device
         Attached: 1
    Controller ID: 0x0
Vendor/Product ID: 0x0C76, 0x161F
        FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub (USB 3.0)
| Vendor/Product ID: 0x8086, 0xA12F
| Matching Device ID: USB\ROOT_HUB30
| Service: USBHUB3
| Driver: USBHUB3.SYS, 11/9/2018 03:49:37, 565048 bytes
| 
+-+ Generic USB Hub
| | Vendor/Product ID: 0x17EF, 0x1010
| | Location: Port_#0004.Hub_#0001
| | Matching Device ID: USB\USB20_HUB
| | Service: USBHUB3
| | Driver: USBHUB3.SYS, 11/9/2018 03:49:37, 565048 bytes
| | 
| +-+ Generic USB Hub
| | | Vendor/Product ID: 0x05AC, 0x1005
| | | Location: Port_#0002.Hub_#0002
| | | Matching Device ID: USB\USB20_HUB
| | | Service: USBHUB3
| | | Driver: USBHUB3.SYS, 11/9/2018 03:49:37, 565048 bytes
| | | 
| | +-+ USB Composite Device
| | | | Vendor/Product ID: 0x05AC, 0x021E
| | | | Location: Port_#0002.Hub_#0004
| | | | Matching Device ID: USB\COMPOSITE
| | | | Service: usbccgp
| | | | Driver: usbccgp.sys, 4/12/2018 00:33:52, 168864 bytes
| | | | 
| | | +-+ Apple Keyboard
| | | | | Vendor/Product ID: 0x05AC, 0x021E
| | | | | Location: 0000.0014.0000.004.002.002.000.000.000
| | | | | Matching Device ID: usb\vid_05ac&pid_021e&mi_00
| | | | | Lower Filters: KeyMagic
| | | | | Service: HidUsb
| | | | | Driver: KeyMagic.sys, 1/21/2014 15:21:26, 31232 bytes
| | | | | Driver: hidusb.sys, 4/12/2018 00:33:52, 42496 bytes
| | | | | Driver: hidclass.sys, 4/12/2018 00:33:52, 173568 bytes
| | | | | Driver: hidparse.sys, 3/6/2019 09:33:02, 46080 bytes
| | | | | Driver: WdfCoInstaller01005.dll, 1/21/2014 15:21:26, 1919968 bytes
| | | | | 
| | | | +-+ HID Keyboard Device
| | | | | | Vendor/Product ID: 0x05AC, 0x021E
| | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | | | Service: kbdhid
| | | | | | Driver: kbdhid.sys, 4/12/2018 00:33:52, 40448 bytes
| | | | | | Driver: kbdclass.sys, 4/12/2018 00:33:52, 63904 bytes
| | | | 
| | +-+ USB Input Device
| | | | Vendor/Product ID: 0x045E, 0x076C
| | | | Location: Port_#0003.Hub_#0004
| | | | Matching Device ID: USB\Class_03&SubClass_01
| | | | Service: HidUsb
| | | | Driver: hidusb.sys, 4/12/2018 00:33:52, 42496 bytes
| | | | Driver: hidclass.sys, 4/12/2018 00:33:52, 173568 bytes
| | | | Driver: hidparse.sys, 3/6/2019 09:33:02, 46080 bytes
| | | | 
| | | +-+ HID-compliant mouse
| | | | | Vendor/Product ID: 0x045E, 0x076C
| | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE
| | | | | Service: mouhid
| | | | | Driver: mouhid.sys, 4/12/2018 00:33:52, 33280 bytes
| | | | | Driver: mouclass.sys, 4/12/2018 00: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 00:33:52, 105984 bytes
| Driver: kbdclass.sys, 4/12/2018 00:33:52, 63904 bytes
| 
+ Synaptics Pointing Device
| Matching Device ID: acpi\len005b
| Upper Filters: SynTP
| Service: i8042prt
| Driver: SynTP.sys, 8/14/2019 01:42:52, 705456 bytes
| Driver: Smb_driver_Intel_Aux.sys, 8/14/2019 01:42:58, 38320 bytes
| Driver: Smb_driver_AMDASF_Aux.sys, 8/14/2019 01:42:56, 37296 bytes
| Driver: SynRMIHID_Aux.sys, 8/14/2019 01:42:52, 49584 bytes
| Driver: SynTPAPI.dll, 8/14/2019 01:43:20, 267184 bytes
| Driver: SynCOM.dll, 8/14/2019 01:43:18, 789936 bytes
| Driver: SynTPRes.dll, 8/14/2019 01:44:30, 18170288 bytes
| Driver: SynTPCpl.dll, 8/14/2019 01:43:26, 4000176 bytes
| Driver: SynCntxt.rtf, 10/31/2018 22:30:40, 6653168 bytes
| Driver: SynZMetr.exe, 8/14/2019 01:43:04, 1894320 bytes
| Driver: SynMood.exe, 8/14/2019 01:43:02, 1921456 bytes
| Driver: SynTPEnh.exe, 8/14/2019 01:43:00, 4194736 bytes
| Driver: Tutorial.exe, 8/14/2019 01:43:06, 1891248 bytes
| Driver: InstNT.exe, 8/14/2019 01:43:16, 325040 bytes
| Driver: SynISDLL.dll, 8/14/2019 01:43:28, 269232 bytes
| Driver: SynUnst.ini, 8/14/2019 01:31:36, 1989966 bytes
| Driver: SynRemoveUserSettings.dat, 4/17/2017 18:12:32, 1315 bytes
| Driver: SynTPHelper.exe, 8/14/2019 01:43:02, 204720 bytes
| Driver: SynTPEnhService.exe, 8/14/2019 01:43:16, 254384 bytes
| Driver: SynTPLpr.exe, 8/14/2019 01:43:12, 215984 bytes
| Driver: TP4table.dat, 4/17/2017 18:12:22, 8027 bytes
| Driver: TP4Sc_JP.htm, 4/17/2017 18:12:22, 12801 bytes
| Driver: TP4Sc_GR.htm, 4/17/2017 18:12:22, 14792 bytes
| Driver: TP4Sc_IT.htm, 4/17/2017 18:12:22, 14300 bytes
| Driver: TP4Sc_SP.htm, 4/17/2017 18:12:22, 13687 bytes
| Driver: TP4Sc_FR.htm, 4/17/2017 18:12:22, 13545 bytes
| Driver: TP4Sc_FI.htm, 4/17/2017 18:12:22, 15345 bytes
| Driver: TP4Sc_NL.htm, 4/17/2017 18:12:22, 13896 bytes
| Driver: TP4Sc_NO.htm, 4/17/2017 18:12:22, 12976 bytes
| Driver: TP4Sc_DK.htm, 4/17/2017 18:12:22, 13551 bytes
| Driver: TP4Sc_SE.htm, 4/17/2017 18:12:22, 12834 bytes
| Driver: TP4Sc_CH.htm, 4/17/2017 18:12:22, 11254 bytes
| Driver: TP4Sc_TW.htm, 4/17/2017 18:12:22, 11070 bytes
| Driver: TP4Sc_TZ.htm, 4/17/2017 18:12:22, 11070 bytes
| Driver: TP4Sc_RU.htm, 4/17/2017 18:12:22, 18621 bytes
| Driver: TP4Sc_BR.htm, 4/17/2017 18:12:22, 14657 bytes
| Driver: TP4Scrol.htm, 4/17/2017 18:12:22, 13233 bytes
| Driver: TP4Sc_JP-win8.htm, 4/17/2017 18:12:22, 13331 bytes
| Driver: TP4Sc_GR-win8.htm, 4/17/2017 18:12:22, 15322 bytes
| Driver: TP4Sc_IT-win8.htm, 4/17/2017 18:12:22, 14830 bytes
| Driver: TP4Sc_SP-win8.htm, 4/17/2017 18:12:22, 14220 bytes
| Driver: TP4Sc_FR-win8.htm, 4/17/2017 18:12:22, 14075 bytes
| Driver: TP4Sc_FI-win8.htm, 4/17/2017 18:12:22, 15868 bytes
| Driver: TP4Sc_NL-win8.htm, 4/17/2017 18:12:22, 14426 bytes
| Driver: TP4Sc_NO-win8.htm, 4/17/2017 18:12:22, 13506 bytes
| Driver: TP4Sc_DK-win8.htm, 4/17/2017 18:12:22, 14081 bytes
| Driver: TP4Sc_SE-win8.htm, 4/17/2017 18:12:22, 13364 bytes
| Driver: TP4Sc_CH-win8.htm, 4/17/2017 18:12:22, 11784 bytes
| Driver: TP4Sc_TW-win8.htm, 4/17/2017 18:12:22, 11603 bytes
| Driver: TP4Sc_TZ-win8.htm, 4/17/2017 18:12:22, 11596 bytes
| Driver: TP4Sc_RU-win8.htm, 4/17/2017 18:12:22, 19151 bytes
| Driver: TP4Sc_BR-win8.htm, 4/17/2017 18:12:22, 15187 bytes
| Driver: TP4Scrol-win8.htm, 4/17/2017 18:12:22, 13763 bytes
| Driver: TP4-A123.GIF, 4/17/2017 18:12:22, 43499 bytes
| Driver: TP4-ASR.GIF, 4/17/2017 18:12:22, 120911 bytes
| Driver: TP4-HEAD.GIF, 4/17/2017 18:12:22, 22797 bytes
| Driver: TP4-I.JPG, 4/17/2017 18:12:22, 894 bytes
| Driver: TP4-IMG.JPG, 4/17/2017 18:12:22, 756 bytes
| Driver: TP4-ISR.JPG, 4/17/2017 18:12:22, 753 bytes
| Driver: TP4-MG.GIF, 4/17/2017 18:12:22, 26890 bytes
| Driver: TP4-NOTE.GIF, 4/17/2017 18:12:22, 201 bytes
| Driver: TP4-SC.GIF, 4/17/2017 18:12:22, 73657 bytes
| Driver: TP4SCROL.CSS, 4/17/2017 18:12:22, 5537 bytes
| Driver: SynTappingNB.wmv, 4/17/2017 18:12:32, 67389 bytes
| Driver: Syn2FingerRightClickNB.wmv, 4/17/2017 18:12:42, 190451 bytes
| Driver: SynVHCoastingNB.wmv, 4/17/2017 18:12:24, 1979037 bytes
| Driver: SynEdgePullsNB.wmv, 4/17/2017 18:12:36, 1184745 bytes
| Driver: SynPalmCheckNB.wmv, 4/17/2017 18:12:34, 266961 bytes
| Driver: SynLinearScrollingNB.wmv, 4/17/2017 18:12:34, 478081 bytes
| Driver: SynPinchZoomNB.wmv, 4/17/2017 18:12:32, 350007 bytes
| Driver: SynSensitivityNB.wmv, 4/17/2017 18:12:32, 172829 bytes
| Driver: SynMomentumNB.wmv, 4/17/2017 18:12:34, 223323 bytes
| Driver: SynTapZonesNB.wmv, 4/17/2017 18:12:32, 206887 bytes
| Driver: SynTapZonesNB_win8.wmv, 4/17/2017 18:12:32, 155875 bytes
| Driver: SynEdgeMotionNB.wmv, 4/17/2017 18:12:36, 782207 bytes
| Driver: SynSlowMotionNB.wmv, 4/17/2017 18:12:32, 239337 bytes
| Driver: SynConstrainedMotionNB.wmv, 4/17/2017 18:12:36, 1122071 bytes
| Driver: SynWindowConstrainedNB.wmv, 4/17/2017 18:12:24, 239325 bytes
| Driver: Syn3FHSlide.wmv, 4/17/2017 18:12:40, 243720 bytes
| Driver: Syn3FHSlideNB.wmv, 4/17/2017 18:12:40, 202757 bytes
| Driver: Syn3FTapActionCenter.wmv, 4/17/2017 18:12:40, 108227 bytes
| Driver: Syn3FTapActionCenterNB.wmv, 4/17/2017 18:12:40, 105076 bytes
| Driver: Syn3FTapCortana.wmv, 4/17/2017 18:12:40, 111378 bytes
| Driver: Syn3FTapCortanaNB.wmv, 4/17/2017 18:12:40, 108227 bytes
| Driver: Syn4FTapActionCenter.wmv, 4/17/2017 18:12:38, 111378 bytes
| Driver: Syn4FTapActionCenterNB.wmv, 4/17/2017 18:12:38, 108227 bytes
| Driver: Syn4FTapCortana.wmv, 4/17/2017 18:12:38, 114529 bytes
| Driver: Syn4FTapCortanaNB.wmv, 4/17/2017 18:12:38, 111378 bytes
| Driver: Syn3FClickActionCenterNB.wmv, 4/17/2017 18:12:40, 139737 bytes
| Driver: Syn3FClickCortanaNB.wmv, 4/17/2017 18:12:40, 149190 bytes
| Driver: Syn4FClickActionCenterNB.wmv, 4/17/2017 18:12:40, 158643 bytes
| Driver: Syn4FClickCortanaNB.wmv, 4/17/2017 18:12:40, 164945 bytes
| Driver: Syn3FVSlide.wmv, 4/17/2017 18:12:40, 395018 bytes
| Driver: Syn3FVSlideWin10.wmv, 1/16/2018 15:18:58, 255312 bytes
| Driver: Syn3FVSlideNB.wmv, 4/17/2017 18:12:40, 363508 bytes
| Driver: Syn3FVSlideNBWin10.wmv, 1/16/2018 15:18:58, 233210 bytes
| Driver: dpinst.exe, 8/14/2019 01:43:14, 1049008 bytes
| Driver: SynSmbDrv.ini, 8/14/2019 01:31:38, 6309 bytes
| Driver: SynRMIHID.ini, 8/14/2019 01:31:38, 3313 bytes
| Driver: SynPinchZoom.wmv, 4/17/2017 18:12:32, 361085 bytes
| Driver: SynMomentum.wmv, 4/17/2017 18:12:34, 231541 bytes
| Driver: SynLinearScrolling.wmv, 4/17/2017 18:12:34, 486299 bytes
| Driver: SynLinearHScrolling.wmv, 4/17/2017 18:12:36, 527389 bytes
| Driver: SynChiralScrolling.wmv, 4/17/2017 18:12:38, 1776645 bytes
| Driver: SynChiralHScrolling.wmv, 4/17/2017 18:12:38, 526657 bytes
| Driver: Syn2FingerScrolling.wmv, 4/17/2017 18:12:42, 650659 bytes
| Driver: Syn2FingerScrollingNB.wmv, 4/17/2017 18:12:40, 634223 bytes
| Driver: Syn2FingerScrollingNB_win8.wmv, 4/17/2017 18:12:40, 387964 bytes
| Driver: Syn2FingerHScrolling.wmv, 4/17/2017 18:12:42, 626005 bytes
| Driver: Syn2FingerHScrollingNB_win8.wmv, 4/17/2017 18:12:42, 421117 bytes
| Driver: Syn3FingerFlick.wmv, 4/17/2017 18:12:40, 774019 bytes
| Driver: Syn3FingerPress.wmv, 4/17/2017 18:12:40, 149361 bytes
| Driver: SynTapHoldToDragNB.wmv, 4/17/2017 18:12:32, 56465 bytes
| Driver: SynTwistRotate.wmv, 4/17/2017 18:12:24, 535667 bytes
| Driver: SynTwistRotateNB.wmv, 6/15/2016 16:41:34, 527449 bytes
| Driver: SynChiralRotate.wmv, 4/17/2017 18:12:38, 321969 bytes
| Driver: SynPivotRotate.wmv, 4/17/2017 18:12:32, 609629 bytes
| Driver: Syn2FingerRotate.wmv, 4/17/2017 18:12:42, 419415 bytes
| Driver: Syn2FingerRotateNB.wmv, 6/15/2016 16:41:16, 398519 bytes
| Driver: SynCoverGesture.wmv, 4/17/2017 18:12:36, 633185 bytes
| Driver: Syn4FingerFlick.wmv, 4/17/2017 18:12:40, 795115 bytes
| Driver: Syn4FingerFlick_win8.wmv, 4/17/2017 18:12:40, 598023 bytes
| Driver: SynCombinationEdgePullsNB.wmv, 4/17/2017 18:12:36, 365982 bytes
| Driver: SynCombinationEdgePullsNB_WithoutRightEx.wmv, 4/17/2017 18:12:36, 388713 bytes
| Driver: Syn2FingerTappingNB.wmv, 4/17/2017 18:12:40, 101711 bytes
| Driver: LenovoShortcut.lnk, 4/17/2017 18:12:42, 2564 bytes
| Driver: SynLenovoHelper.exe, 8/14/2019 01:44:28, 147376 bytes
| Driver: SynCom.dll, 8/14/2019 01:43:20, 419248 bytes
| Driver: Mouse Properties (Touchpad Clickpad Trackpad TrackPoint Mouse Pointer Pointing Pad).lnk, 4/17/2017 18:12:42, 2564 bytes
| Driver: mouclass.sys, 4/12/2018 00:33:52, 56728 bytes
| Driver: i8042prt.sys, 4/12/2018 00:33:52, 105984 bytes
| Driver: SynTPCo50-11.dll, 8/14/2019 01:43:30, 334768 bytes
| Driver: WdfCoInstaller01011.dll, 4/17/2017 18:12:20, 1795952 bytes

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 57.4 GB
Total Space: 243.8 GB
File System: NTFS
      Model: TOSHIBA THNSFJ256GDNU A

      Drive: D:
 Free Space: 38.1 GB
Total Space: 953.9 GB
File System: NTFS
      Model: HGST HTS541010A7E630

      Drive: E:
 Free Space: 1.3 GB
Total Space: 2.0 GB
File System: NTFS
      Model: n/a

      Drive: G:
      Model: ELBY CLONEDRIVE SCSI CdRom Device
     Driver: c:\windows\system32\drivers\cdrom.sys, 10.00.17134.0137 (German), 10/23/2018 11:16:50, 159744 bytes

--------------
System Devices
--------------
     Name: Intel(R) HD Graphics 530
Device ID: PCI\VEN_8086&DEV_191B&SUBSYS_222E17AA&REV_06\3&B1BFB68&0&10
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdkmd64.sys, 26.20.0100.7106 (English), 8/22/2019 03:06:00, 20112928 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iglhxs64.vp, 8/22/2019 02:49:38, 5066 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd10iumd64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:24, 20657480 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd11dxva64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:28, 63958888 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd12dxva64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:32, 63849800 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd12umd64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:36, 19196104 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdgmm64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:44, 1255928 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxcmrt64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:56, 218360 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfx11cmrt64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:54, 217336 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdumdim64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:52, 1832184 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd9dxva64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:40, 63860744 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdail64.dll, 8/22/2019 03:05:58, 187376 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iga64.dll, 8/22/2019 06:06:16, 3842232 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igc64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:20, 37517608 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\UniversalAdapter64.dll, 8/22/2019 06:07:08, 276640 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\common_clang64.dll, 2.00.0007.0000 (English), 8/22/2019 06:06:16, 72445032 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdfcl64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:44, 899000 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdmd64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:48, 5520128 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdml64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:50, 2216312 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdde64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:42, 458424 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdinfo64.dll, 8/22/2019 06:06:46, 145456 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdext64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:42, 404856 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd10idpp64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:22, 662128 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd10iumd32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:22, 19483112 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd11dxva32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:26, 62444360 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd12dxva32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:30, 62357864 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd12umd32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:34, 18857992 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdgmm32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:44, 1063416 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdumdim32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:52, 1613080 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd9dxva32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:38, 62357768 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdail32.dll, 8/22/2019 03:05:56, 165872 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxcmrt32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:54, 187896 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfx11cmrt32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:54, 186872 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iga32.dll, 8/22/2019 06:06:16, 3312408 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igc32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:18, 33496968 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\UniversalAdapter32.dll, 8/22/2019 06:07:08, 236256 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\common_clang32.dll, 2.00.0007.0000 (English), 8/22/2019 06:06:14, 54407272 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdfcl32.dll, 26.20.0100.7106 (English), 8/22/2019 03:05:58, 817160 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdmd32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:46, 3996800 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdml32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:48, 1645592 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdde32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:40, 374488 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdinfo32.dll, 8/22/2019 06:06:46, 127992 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdext32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:42, 320408 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igd10idpp32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:20, 644208 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iglhxo64.vp, 8/22/2019 02:49:38, 42513 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iglhxc64.vp, 8/22/2019 02:49:38, 44194 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iglhxg64.vp, 8/22/2019 02:49:38, 43760 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iglhxo64_dev.vp, 8/22/2019 02:49:38, 43143 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iglhxc64_dev.vp, 8/22/2019 02:49:38, 43214 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iglhxg64_dev.vp, 8/22/2019 02:49:38, 43732 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iglhxa64.vp, 8/22/2019 02:49:38, 1125 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\iglhxa64.cpa, 8/22/2019 02:49:38, 1376256 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\IntelCpHDCPSvc.exe, 25.20.0100.7106 (English), 8/22/2019 03:06:16, 508448 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\cp_resources.bin, 8/22/2019 02:49:30, 1470092 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\difx64.exe, 1.04.0005.0000 (English), 8/22/2019 03:05:50, 274976 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxDH.dll, 6.15.0100.7106 (English), 8/22/2019 03:06:06, 1112048 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxDI.dll, 6.15.0100.7106 (English), 8/22/2019 03:06:06, 445424 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxLHM.dll, 6.15.0100.7106 (English), 8/22/2019 03:06:10, 2264584 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxEM.exe, 6.15.0100.7106 (English), 8/22/2019 03:06:08, 1020960 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxCUIServicePS.dll, 8/22/2019 03:06:04, 412144 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxCUIService.exe, 6.15.0100.7106 (English), 8/22/2019 03:06:04, 400952 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxDHLib.dll, 1.00.0000.0000 (Invariant Language), 8/22/2019 03:06:06, 123888 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxLHMLib.dll, 1.00.0000.0000 (Invariant Language), 8/22/2019 03:06:12, 22512 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\GfxUIEx.exe, 6.15.0100.7106 (English), 8/22/2019 03:05:52, 505888 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\Gfxv4_0.exe, 8.15.0100.7106 (German), 8/22/2019 03:05:54, 1122328 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\GfxResources.dll, 8.15.0100.7106 (German), 8/22/2019 03:05:52, 9335280 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\MetroIntelGenericUIFramework.dll, 1.00.0000.0000 (German), 8/22/2019 03:06:22, 646128 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxCPL.cpl, 8/22/2019 03:06:02, 284656 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxDTCM.dll, 6.15.0100.7106 (English), 8/22/2019 03:06:08, 188912 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxext.exe, 6.15.0100.7106 (English), 8/22/2019 03:06:10, 355360 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxexps.dll, 6.15.0010.3682 (English), 8/22/2019 06:06:56, 58648 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\GfxDownloadWrapper.exe, 8.15.0100.7106 (German), 8/22/2019 03:05:50, 162840 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxSDK.exe, 8/22/2019 03:06:12, 1054776 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxSDKLib.dll, 1.00.0000.0000 (Invariant Language), 8/22/2019 03:06:14, 99824 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ColorImageEnhancement.wmv, 8/22/2019 02:49:30, 375173 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ImageStabilization.wmv, 8/22/2019 02:49:38, 403671 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\FilmModeDetection.wmv, 8/22/2019 02:49:30, 641530 bytes
   Driver: C:\Windows\system32\igfxCPL.cpl, 8/22/2019 03:06:02, 284656 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igfxexps32.dll, 6.15.0010.3682 (English), 8/22/2019 03:06:10, 52720 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igvk64.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:58, 10295448 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igvk64.json, 8/22/2019 02:49:38, 137 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\VulkanRT-EULA.txt, 8/22/2019 02:49:44, 3633 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igvk32.dll, 26.20.0100.7106 (English), 8/22/2019 06:06:56, 9128856 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igvk32.json, 8/22/2019 02:49:38, 137 bytes
   Driver: C:\Windows\system32\vulkan-1.dll, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 1024280 bytes
   Driver: C:\Windows\system32\vulkaninfo.exe, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 307232 bytes
   Driver: C:\Windows\system32\vulkan-1-999-0-0-0.dll, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 1024280 bytes
   Driver: C:\Windows\system32\vulkaninfo-1-999-0-0-0.exe, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 307232 bytes
   Driver: C:\Windows\SysWow64\vulkan-1.dll, 1.01.0108.0000 (English), 8/22/2019 03:06:26, 888088 bytes
   Driver: C:\Windows\SysWow64\vulkaninfo.exe, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 280608 bytes
   Driver: C:\Windows\SysWow64\vulkan-1-999-0-0-0.dll, 1.01.0108.0000 (English), 8/22/2019 03:06:26, 888088 bytes
   Driver: C:\Windows\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 280608 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\OSSCOPYRIGHT, 8/22/2019 02:49:44, 1372 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ig9icd64.dll, 26.20.0100.7106 (English), 8/22/2019 03:05:56, 15955464 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ig9icd32.dll, 26.20.0100.7106 (English), 8/22/2019 03:05:56, 12603888 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\llvm_release_license.txt, 8/22/2019 02:49:46, 1937 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\readme.txt, 8/22/2019 02:49:46, 9710 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\version.ini, 8/22/2019 02:49:46, 30 bytes
   Driver: C:\Windows\SysWow64\Intel_OpenCL_ICD32.dll, 2.02.0001.0000 (English), 8/22/2019 03:06:20, 108016 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\task_executor32.dll, 7.06.0000.0228 (English), 8/22/2019 03:07:04, 353264 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\OclCpuBackend32.dll, 7.06.0000.0228 (English), 8/22/2019 03:07:04, 17799152 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\intelocl32.dll, 7.06.0000.0228 (English), 8/22/2019 03:07:02, 1099248 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\cpu_device32.dll, 7.06.0000.0228 (English), 8/22/2019 03:07:02, 418288 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clbltfnn8.rtl, 8/22/2019 02:49:46, 2759352 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clbltfnn8_img_cbk.o, 8/22/2019 02:49:46, 388904 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clbltfnn8_img_cbk.rtl, 8/22/2019 02:49:46, 997840 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clbltfng9.rtl, 8/22/2019 02:49:46, 2716988 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clbltfng9_img_cbk.o, 8/22/2019 02:49:46, 376324 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clbltfng9_img_cbk.rtl, 8/22/2019 02:49:46, 999012 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clbltfns9.rtl, 8/22/2019 02:49:46, 1720252 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clbltfns9_img_cbk.o, 8/22/2019 02:49:46, 331732 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clbltfns9_img_cbk.rtl, 8/22/2019 02:49:46, 884792 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\clang_compiler32.dll, 7.06.0000.0228 (English), 8/22/2019 03:07:00, 3079664 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\__ocl_svml_n8.dll, 3.06.0002.0000 (English), 8/22/2019 03:07:06, 7164912 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\__ocl_svml_g9.dll, 3.06.0002.0000 (English), 8/22/2019 03:07:04, 6313456 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\__ocl_svml_s9.dll, 3.06.0002.0000 (English), 8/22/2019 03:07:06, 6120944 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\tbb\ocltbbmalloc32.dll, 2018.00.2018.0820 (German), 8/22/2019 03:07:08, 591072 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x86\tbb\ocltbb32.dll, 2018.00.2018.0820 (German), 8/22/2019 03:07:08, 699104 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\clbltfnshared.rtl, 8/22/2019 02:49:46, 1772864 bytes
   Driver: C:\Windows\system32\Intel_OpenCL_ICD64.dll, 2.02.0001.0000 (English), 8/22/2019 03:06:20, 121328 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\task_executor64.dll, 7.06.0000.0228 (English), 8/22/2019 03:06:56, 439280 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\OclCpuBackend64.dll, 7.06.0000.0228 (English), 8/22/2019 03:06:54, 23319024 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\intelocl64.dll, 7.06.0000.0228 (English), 8/22/2019 03:06:54, 1426928 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\cpu_device64.dll, 7.06.0000.0228 (English), 8/22/2019 03:06:52, 527856 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clbltfnh8.rtl, 8/22/2019 02:49:46, 2752472 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clbltfnh8_img_cbk.o, 8/22/2019 02:49:46, 443424 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clbltfnh8_img_cbk.rtl, 8/22/2019 02:49:46, 1072384 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clbltfne9.rtl, 8/22/2019 02:49:46, 2710936 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clbltfne9_img_cbk.o, 8/22/2019 02:49:46, 424408 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clbltfne9_img_cbk.rtl, 8/22/2019 02:49:46, 1073556 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clbltfnl9.rtl, 8/22/2019 02:49:46, 1726120 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clbltfnl9_img_cbk.o, 8/22/2019 02:49:46, 368472 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clbltfnl9_img_cbk.rtl, 8/22/2019 02:49:46, 959368 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\clang_compiler64.dll, 7.06.0000.0228 (English), 8/22/2019 03:06:52, 4104688 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\__ocl_svml_h8.dll, 3.06.0002.0000 (English), 8/22/2019 03:06:58, 7455728 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\__ocl_svml_e9.dll, 3.06.0002.0000 (English), 8/22/2019 03:06:56, 6800880 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\__ocl_svml_l9.dll, 3.06.0002.0000 (English), 8/22/2019 03:06:58, 6612488 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\tbb\ocltbbmalloc64.dll, 2018.00.2018.0820 (German), 8/22/2019 03:07:00, 813816 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\ocl\bin\x64\tbb\ocltbb64.dll, 2018.00.2018.0820 (German), 8/22/2019 03:07:00, 943320 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\IntelOpenCL32.dll, 26.20.0100.7106 (English), 8/22/2019 03:06:18, 1159152 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdrcl32.dll, 23.20.0100.7106 (English), 8/22/2019 03:06:02, 3454448 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\IntelOpenCL64.dll, 26.20.0100.7106 (English), 8/22/2019 03:06:18, 1485296 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igdrcl64.dll, 23.20.0100.7106 (English), 8/22/2019 03:06:02, 3931120 bytes
   Driver: C:\Windows\SysWow64\libEGL.dll, 8/22/2019 03:06:20, 136688 bytes
   Driver: C:\Windows\SysWow64\libGLESv1_CM.dll, 8/22/2019 03:06:22, 141808 bytes
   Driver: C:\Windows\SysWow64\libGLESv2.dll, 8/22/2019 03:06:22, 168944 bytes
   Driver: C:\Program Files\Intel\Media SDK\libmfxhw32.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:00, 19995752 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfxplugin32_hw.dll, 1.19.0007.0010 (English), 8/22/2019 03:06:24, 11912176 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_32.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:04, 2596456 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_32.dll, 9.19.0007.0010 (English), 8/22/2019 03:06:26, 2439664 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_32.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:04, 2610056 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_32.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:06, 2605352 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_32.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:02, 2438696 bytes
   Driver: C:\Program Files\Intel\Media SDK\c_32.cpa, 6/26/2019 02:16:08, 1361159 bytes
   Driver: C:\Program Files\Intel\Media SDK\cpa_32.vp, 8/22/2019 02:49:30, 1125 bytes
   Driver: C:\Program Files\Intel\Media SDK\dev_32.vp, 8/22/2019 02:49:30, 57143 bytes
   Driver: C:\Program Files\Intel\Media SDK\he_32.vp, 8/22/2019 02:49:32, 70745 bytes
   Driver: C:\Program Files\Intel\Media SDK\mj_32.vp, 8/22/2019 02:49:44, 65793 bytes
   Driver: C:\Program Files\Intel\Media SDK\h265e_32.vp, 8/22/2019 02:49:32, 72405 bytes
   Driver: C:\Program Files\Intel\Media SDK\vp9e_32.vp, 8/22/2019 02:49:44, 71912 bytes
   Driver: C:\Program Files\Intel\Media SDK\libmfxhw64.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:02, 21093752 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfxplugin64_hw.dll, 1.19.0007.0010 (English), 8/22/2019 03:06:24, 25065968 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_64.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:04, 3201224 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_64.dll, 9.19.0007.0010 (English), 8/22/2019 03:06:26, 3007472 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_64.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:06, 3221160 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_64.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:06, 3214312 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_64.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:02, 2995208 bytes
   Driver: C:\Program Files\Intel\Media SDK\c_64.cpa, 6/26/2019 02:16:08, 1376256 bytes
   Driver: C:\Program Files\Intel\Media SDK\cpa_64.vp, 8/22/2019 02:49:30, 1125 bytes
   Driver: C:\Program Files\Intel\Media SDK\dev_64.vp, 8/22/2019 02:49:30, 56359 bytes
   Driver: C:\Program Files\Intel\Media SDK\he_64.vp, 8/22/2019 02:49:32, 13545 bytes
   Driver: C:\Program Files\Intel\Media SDK\mj_64.vp, 8/22/2019 02:49:44, 13281 bytes
   Driver: C:\Program Files\Intel\Media SDK\h265e_64.vp, 8/22/2019 02:49:32, 14121 bytes
   Driver: C:\Program Files\Intel\Media SDK\vp9e_64.vp, 8/22/2019 02:49:44, 13956 bytes
   Driver: C:\Windows\system32\intel_gfx_api-x64.dll, 8.18.0008.0030 (English), 8/22/2019 06:06:58, 212440 bytes
   Driver: C:\Windows\SysWow64\intel_gfx_api-x86.dll, 8.18.0008.0030 (English), 8/22/2019 06:07:00, 184120 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\libmfxhw64.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:02, 21093752 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\mfxplugin64_hw.dll, 1.19.0007.0010 (English), 8/22/2019 03:06:24, 25065968 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\intel_gfx_api-x64.dll, 8.18.0008.0030 (English), 8/22/2019 06:06:58, 212440 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\libmfxhw32.dll, 9.19.0007.0010 (English), 8/22/2019 06:07:00, 19995752 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\mfxplugin32_hw.dll, 1.19.0007.0010 (English), 8/22/2019 03:06:24, 11912176 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\intel_gfx_api-x86.dll, 8.18.0008.0030 (English), 8/22/2019 06:07:00, 184120 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\IntelCpHeciSvc.exe, 9.01.0001.1117 (English), 8/22/2019 03:06:16, 508960 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_959c9903750fbcbe\igxpco64.dll, 1.03.0025.0000 (English), 8/22/2019 03:06:14, 234992 bytes

     Name: High Definition Audio Controller
Device ID: PCI\VEN_8086&DEV_A170&SUBSYS_222E17AA&REV_31\3&B1BFB68&0&FB
   Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 10.00.17134.0001 (English), 4/12/2018 00:33:45, 86016 bytes
   Driver: C:\Windows\system32\DRIVERS\drmk.sys, 10.00.17134.0001 (English), 4/12/2018 00:33:46, 98304 bytes
   Driver: C:\Windows\system32\DRIVERS\portcls.sys, 10.00.17134.0001 (English), 4/12/2018 00:33:46, 379392 bytes

     Name: Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #3 - A112
Device ID: PCI\VEN_8086&DEV_A112&SUBSYS_222E17AA&REV_F1\3&B1BFB68&0&E2
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.17134.1067 (English), 10/2/2019 06:19:52, 374584 bytes

     Name: Intel(R) Ethernet Connection (2) I219-LM
Device ID: PCI\VEN_8086&DEV_15B7&SUBSYS_223317AA&REV_31\3&B1BFB68&0&FE
   Driver: n/a

     Name: Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #5 - A114
Device ID: PCI\VEN_8086&DEV_A114&SUBSYS_222E17AA&REV_F1\3&B1BFB68&0&E4
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.17134.1067 (English), 10/2/2019 06:19:52, 374584 bytes

     Name: NVIDIA Quadro M1000M
Device ID: PCI\VEN_10DE&DEV_13B1&SUBSYS_222E17AA&REV_A2\4&26BA905&0&0008
   Driver: C:\Windows\system32\DRIVERS\NVIDIA Corporation\Drs\dbInstaller.exe, 26.21.0014.3194 (English), 10/3/2019 00:01:30, 732872 bytes
   Driver: C:\Windows\system32\DRIVERS\NVIDIA Corporation\Drs\nvdrsdb.bin, 9/20/2019 05:04:24, 1589596 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\NvContainerSetup.exe, 1.00.0010.0000 (German), 10/3/2019 00:02:02, 4551216 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\NvCplSetupInt.exe, 1.00.0010.0000 (German), 10/3/2019 00:02:02, 102799248 bytes
   Driver: C:\Program Files\NVIDIA Corporation\license.txt, 4/23/2019 17:17:58, 27203 bytes
   Driver: C:\Program Files\NVIDIA Corporation\NVSMI\MCU.exe, 1.01.5204.20580 (German), 10/3/2019 00:01:40, 858040 bytes
   Driver: C:\Program Files\NVIDIA Corporation\NVSMI\nvdebugdump.exe, 6.14.0014.3194 (English), 10/3/2019 00:02:14, 449952 bytes
   Driver: C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.1.pdf, 9/20/2019 05:04:24, 104564 bytes
   Driver: C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.exe, 8.17.0014.3194 (English), 10/3/2019 00:02:26, 573552 bytes
   Driver: C:\Program Files\NVIDIA Corporation\NVSMI\nvml.dll, 8.17.0014.3194 (English), 10/3/2019 00:02:38, 1007192 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvopencl32.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:56, 29849984 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvopencl64.dll, 26.21.0014.3194 (English), 10/3/2019 00:03:02, 35353016 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvlddmkm.sys, 26.21.0014.3194 (English), 10/3/2019 00:02:34, 22128032 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nv-vk64.json, 9/20/2019 05:04:24, 669 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvDecMFTMjpeg.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:14, 611744 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvDecMFTMjpegx.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:16, 754264 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvEncMFTH264.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:18, 1141664 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvEncMFTH264x.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:20, 1453144 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvcbl64.dll, 26.21.0014.3194 (English), 10/3/2019 00:01:46, 526208 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvd3dumx.dll, 26.21.0014.3194 (English), 10/2/2019 21:00:32, 21867448 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvd3dumx_cfg.dll, 26.21.0014.3194 (English), 10/2/2019 21:00:38, 22057032 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvdlistx.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:18, 201632 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumdx.dll, 26.21.0014.3194 (English), 10/2/2019 21:00:52, 959152 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvoglv64.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:48, 40988600 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvoptix.dll, 6.01.0002.0000 (English), 10/3/2019 00:03:08, 70433992 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvrtum64.dll, 26.21.0014.3194 (English), 10/3/2019 00:03:26, 24302792 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvwgf2umx.dll, 26.21.0014.3194 (English), 10/2/2019 21:01:04, 39575656 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvwgf2umx_cfg.dll, 26.21.0014.3194 (English), 10/2/2019 21:01:14, 40064592 bytes
   Driver: C:\Windows\system32\NvFBC64.dll, 6.14.0014.3194 (English), 10/3/2019 00:02:24, 2042272 bytes
   Driver: C:\Windows\system32\NvIFR64.dll, 6.14.0014.3194 (English), 10/3/2019 00:02:30, 1471952 bytes
   Driver: C:\Windows\system32\NvIFROpenGL.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:30, 633488 bytes
   Driver: C:\Windows\system32\OpenCL.dll, 2.02.0001.0000 (English), 10/3/2019 00:04:04, 552144 bytes
   Driver: C:\Windows\system32\nvEncodeAPI64.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:22, 811096 bytes
   Driver: C:\Windows\system32\nvapi64.dll, 26.21.0014.3194 (English), 10/2/2019 21:00:24, 5088048 bytes
   Driver: C:\Windows\system32\nvcompiler.dll, 26.21.0014.3194 (English), 10/3/2019 00:01:54, 40411904 bytes
   Driver: C:\Windows\system32\nvcuda.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:08, 20194048 bytes
   Driver: C:\Windows\system32\nvcuvid.dll, 7.17.0014.3194 (English), 10/3/2019 00:02:12, 5425808 bytes
   Driver: C:\Windows\system32\nvfatbinaryLoader.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:22, 1164376 bytes
   Driver: C:\Windows\system32\nvinfo.pb, 9/20/2019 05:04:24, 52612 bytes
   Driver: C:\Windows\system32\nvmcumd.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:36, 822688 bytes
   Driver: C:\Windows\system32\nvofapi64.dll, 10/3/2019 00:02:40, 677280 bytes
   Driver: C:\Windows\system32\nvptxJitCompiler.dll, 26.21.0014.3194 (English), 10/3/2019 00:03:24, 11058616 bytes
   Driver: C:\Windows\system32\vulkan-1-999-0-0-0.dll, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 1024280 bytes
   Driver: C:\Windows\system32\vulkan-1.dll, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 1024280 bytes
   Driver: C:\Windows\system32\vulkaninfo-1-999-0-0-0.exe, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 307232 bytes
   Driver: C:\Windows\system32\vulkaninfo.exe, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 307232 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\DisplayDriverRAS.dll, 1.10.0000.0000 (English), 10/3/2019 00:01:32, 2622848 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nv-vk32.json, 9/20/2019 05:04:24, 669 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nv_Icc_AdvancedColor_Identity.icm, 9/20/2019 05:04:24, 3288 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvd3dum.dll, 26.21.0014.3194 (English), 10/2/2019 21:00:26, 18268416 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvd3dum_cfg.dll, 26.21.0014.3194 (English), 10/2/2019 21:00:44, 18610352 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvdlist.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:18, 176728 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvldumd.dll, 26.21.0014.3194 (English), 10/2/2019 21:00:50, 801224 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvoglv32.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:42, 30452664 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvwgf2um.dll, 26.21.0014.3194 (English), 10/2/2019 21:00:54, 34107056 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\nvwgf2um_cfg.dll, 26.21.0014.3194 (English), 10/2/2019 21:01:22, 34842152 bytes
   Driver: C:\Windows\SysWow64\NvFBC.dll, 6.14.0014.3194 (English), 10/3/2019 00:02:24, 1543640 bytes
   Driver: C:\Windows\SysWow64\NvIFR.dll, 6.14.0014.3194 (English), 10/3/2019 00:02:28, 1136208 bytes
   Driver: C:\Windows\SysWow64\NvIFROpenGL.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:30, 524376 bytes
   Driver: C:\Windows\SysWow64\OpenCL.dll, 2.02.0001.0000 (English), 10/3/2019 00:04:02, 457096 bytes
   Driver: C:\Windows\SysWow64\nvEncodeAPI.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:22, 656528 bytes
   Driver: C:\Windows\SysWow64\nvapi.dll, 26.21.0014.3194 (English), 10/2/2019 21:00:22, 4343224 bytes
   Driver: C:\Windows\SysWow64\nvcompiler.dll, 26.21.0014.3194 (English), 10/3/2019 00:01:48, 35269560 bytes
   Driver: C:\Windows\SysWow64\nvcuda.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:04, 17471184 bytes
   Driver: C:\Windows\SysWow64\nvcuvid.dll, 7.17.0014.3194 (English), 10/3/2019 00:02:10, 4767888 bytes
   Driver: C:\Windows\SysWow64\nvfatbinaryLoader.dll, 26.21.0014.3194 (English), 10/3/2019 00:02:22, 914336 bytes
   Driver: C:\Windows\SysWow64\nvofapi.dll, 10/3/2019 00:02:38, 544160 bytes
   Driver: C:\Windows\SysWow64\nvptxJitCompiler.dll, 26.21.0014.3194 (English), 10/3/2019 00:03:20, 9492680 bytes
   Driver: C:\Windows\SysWow64\vulkan-1-999-0-0-0.dll, 1.01.0108.0000 (English), 8/22/2019 03:06:26, 888088 bytes
   Driver: C:\Windows\SysWow64\vulkan-1.dll, 1.01.0108.0000 (English), 8/22/2019 03:06:26, 888088 bytes
   Driver: C:\Windows\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 280608 bytes
   Driver: C:\Windows\SysWow64\vulkaninfo.exe, 1.01.0108.0000 (English), 8/22/2019 03:06:28, 280608 bytes
   Driver: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_4d81dccb053cedab\NvTelemetry64.dll, 14.03.0015.0000 (English), 10/3/2019 00:03:32, 4417920 bytes
   Driver: C:\Windows\system32\nvdispco6443194.dll, 2.00.0055.0000 (English), 10/3/2019 00:02:16, 1722456 bytes
   Driver: C:\Windows\system32\nvdispgenco6443194.dll, 2.00.0027.0002 (English), 10/3/2019 00:02:16, 1467864 bytes

     Name: Intel(R) Dual Band Wireless-AC 8260
Device ID: PCI\VEN_8086&DEV_24F3&SUBSYS_01308086&REV_3A\4&334743A6&0&00E2
   Driver: C:\Windows\system32\DRIVERS\Netwtw06.sys, 20.70.0012.0005 (English), 8/28/2019 03:09:32, 8831480 bytes
   Driver: C:\Windows\system32\DRIVERS\Netwfw06.dat, 8/28/2019 03:09:32, 2608280 bytes
   Driver: C:\Windows\system32\IntelWifiIhv06.dll, 20.70.0012.0005 (English), 8/28/2019 03:09:32, 1106216 bytes

     Name: Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) PCIe Controller (x16) - 1901
Device ID: PCI\VEN_8086&DEV_1901&SUBSYS_222E17AA&REV_07\3&B1BFB68&0&08
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.17134.1067 (English), 10/2/2019 06:19:52, 374584 bytes

     Name: Intel(R) 100 Series/C230 Series Chipset Family PMC - A121
Device ID: PCI\VEN_8086&DEV_A121&SUBSYS_222E17AA&REV_31\3&B1BFB68&0&FA
   Driver: n/a

     Name: Intel(R) 100 Series/C230 Series Chipset Family LPC Controller (CM236) - A150
Device ID: PCI\VEN_8086&DEV_A150&SUBSYS_222E17AA&REV_31\3&B1BFB68&0&F8
   Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 10.00.17134.0001 (English), 4/12/2018 00:33:49, 18848 bytes

     Name: Realtek PCIE CardReader
Device ID: PCI\VEN_10EC&DEV_525A&SUBSYS_222E17AA&REV_01\4&21324FEB&0&00E8
   Driver: C:\Windows\system32\DRIVERS\RtsPer.sys, 10.00.16299.21304 (English), 10/19/2017 13:39:38, 864704 bytes
   Driver: C:\Windows\SysWOW64\RsCRIcon.dll, 1.10.0000.0000 (English), 4/17/2017 18:12:22, 9891328 bytes

     Name: Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
Device ID: PCI\VEN_8086&DEV_A12F&SUBSYS_222E17AA&REV_31\3&B1BFB68&0&A0
   Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.17134.0001 (English), 4/12/2018 00:33:52, 434592 bytes
   Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.17134.0001 (English), 4/12/2018 00:33:52, 123576 bytes

     Name: Synaptics SMBus Driver
Device ID: PCI\VEN_8086&DEV_A123&SUBSYS_222E17AA&REV_31\3&B1BFB68&0&FC
   Driver: C:\Windows\system32\DRIVERS\Smb_driver_Intel.sys, 19.03.0004.0223 (English), 8/14/2019 01:42:58, 38320 bytes
   Driver: C:\Windows\system32\WdfCoInstaller01011.dll, 1.11.9200.16384 (German), 4/17/2017 18:12:20, 1795952 bytes

     Name: Intel(R) Management Engine Interface 
Device ID: PCI\VEN_8086&DEV_A13A&SUBSYS_222E17AA&REV_31\3&B1BFB68&0&B0
   Driver: C:\Windows\system32\DRIVERS\TeeDriverW8x64.sys, 1914.12.0000.1256 (English), 8/5/2019 12:59:34, 266128 bytes

     Name: Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) Host Bridge/DRAM Registers - 1910
Device ID: PCI\VEN_8086&DEV_1910&SUBSYS_222E17AA&REV_07\3&B1BFB68&0&00
   Driver: n/a

     Name: Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller
Device ID: PCI\VEN_8086&DEV_A102&SUBSYS_222E17AA&REV_31\3&B1BFB68&0&B8
   Driver: C:\Windows\system32\DRIVERS\iaStorAC.sys, 15.09.0004.1041 (English), 4/25/2018 21:48:14, 906216 bytes

     Name: JMicron JMB36X Controller
Device ID: PCI\VEN_197B&DEV_2360&SUBSYS_2360197B&REV_02\4&2F99903&0&00E0
   Driver: C:\Windows\system32\DRIVERS\jraid.sys, 1.17.0065.0011 (English), 9/17/2012 14:05:26, 123704 bytes

     Name: Intel(R) 100 Series/C230 Series Chipset Family Thermal subsystem - A131
Device ID: PCI\VEN_8086&DEV_A131&SUBSYS_222E17AA&REV_31\3&B1BFB68&0&A2
   Driver: n/a

     Name: Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #13 - A11C
Device ID: PCI\VEN_8086&DEV_A11C&SUBSYS_222E17AA&REV_F1\3&B1BFB68&0&E8
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.17134.1067 (English), 10/2/2019 06:19:52, 374584 bytes

     Name: Intel(R) 100 Series/C230 Series Chipset Family PCI Express Root Port #1 - A110
Device ID: PCI\VEN_8086&DEV_A110&SUBSYS_222E17AA&REV_F1\3&B1BFB68&0&E0
   Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.17134.1067 (English), 10/2/2019 06:19:52, 374584 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
Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.17134.1067
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
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.1067
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.1067
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.1067
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
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 (3- USB PnP Audio Device),0x00200000,0,0,qcap.dll,10.00.17134.0001
Microphone Array (Realtek High Definition Audio),0x00200000,0,0,qcap.dll,10.00.17134.0001

PBDA CP Filters:
PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.17134.1067
PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.17134.1067
PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.17134.1067

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:
USB PnP Audio Device,0x00200000,2,2,ksproxy.ax,10.00.17134.0001
Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,10.00.17134.0001

WDM Streaming Rendering Devices:
Realtek HD Audio output,0x00200000,1,1,ksproxy.ax,10.00.17134.0001
USB PnP Audio Device,0x00200000,2,2,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

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

WDM Streaming Communication Transforms:
Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.17134.0001

Audio Renderers:
Speakers (3- USB PnP Audio Device),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 (3- USB PnP Audio Device),0x00200000,1,0,quartz.dll,10.00.17134.0001
DirectSound: Speaker/HP (Realtek High Definition Audio),0x00200000,1,0,quartz.dll,10.00.17134.0001
Speaker/HP (Realtek High Definition Audio),0x00200000,1,0,quartz.dll,10.00.17134.0001


----------------------------
Preferred DirectShow Filters
----------------------------

[HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred]

<media subtype GUID>, [<filter friendly name>, ]<filter CLSID>

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]

<category>:
  <transform friendly name>, <transform CLSID>, <flags>, [<merit>, ]<file name>, <file version>

Video Decoders:
  Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 9.19.0007.0010
  NVIDIA MJPEG Video Decoder MFT, {70F36578-2741-454F-B494-E8563DDD1CB4}, 0x4, 8, nvDecMFTMjpegx.dll, 26.21.0014.3194
  Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.17134.1067
  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.1067
  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
Video Encoders:
  Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 9.19.0007.0010
  NVIDIA H.264 Encoder MFT, {60F44560-5A20-4857-BFEF-D29773CB8040}, 0x4, 8, nvEncMFTH264x.dll, 26.21.0014.3194
  Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 9.19.0007.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.1130
  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.1067
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.1130
  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.1130
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.1067
  GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.17134.1067
  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.1067
  IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.17134.1067
  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.1067
  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.1067
  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.1067
  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.1067
Others:
  Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.17134.1067


--------------------------------------------
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]

<file ext. or MIME type>, <handler CLSID>, <brief description>[, 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]

<URL type>, <handler CLSID>, <brief description>[, 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]

<media subtype GUID>, [<transform friendly name>, ]<transform CLSID>

{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]

<transform CLSID>



------------------------
Disabled Media Sources
------------------------

[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse]

<media source CLSID>


---------------
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 , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


+++ WER1 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


+++ WER2 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


+++ WER3 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


+++ WER4 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


+++ WER5 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


+++ WER6 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


+++ WER7 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


+++ WER8 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


+++ WER9 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1038
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: UpdateOrchestrator
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0


...#SSU#...
