# SSU Scan Information
Scan Info:
 Version:"2.5.0.15"
 Date:"02-23-2022"
 Time:"00:00:39.4197046"

# Scanned Hardware
Computer:
          BaseBoard Manufacturer:"Intel Corporation"
          BIOS Mode:"UEFI"
          BIOS Version/Date:"Intel Corp. BNKBL357.86A.0088.2022.0125.1102 , 01-25-2022 12:00 AM"
          CD or DVD:"Not Available"
          Embedded Controller Version:"8.15"
          Platform Role:"Desktop"
          Processor:"Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz , GenuineIntel"
          Secure Boot State:"Off"
          SMBIOS Version:"3.1"
          Sound Card:"Intel(R) Display Audio"
          Sound Card:"Realtek High Definition Audio"
          System Manufacturer:"Intel(R) Client Systems"
          System Model:"NUC7i5BNH"
          System SKU:"Not Available"
          System Type:"x64-based PC"
          - "Display"
               Intel ® Graphics Driver Version:"24.20.100.6286"
               - "Intel(R) Iris(R) Plus Graphics 640"
                    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) Iris(R) Plus Graphics 640"
                         Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Iris+Plus+Graphics+640"
                    CoInstallers:"oem26.inf,iKBLD_w10_DS,Internal,Intel(R) Iris(R) Graphics Family"
                    Color Table Entries:"4294967296"
                    Dedicated Video Memory:"Not Available"
                    Driver:"igdkmd64.sys"
                    Driver Date:"08-14-2018 05:00 PM"
                    Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdkmd64.sys"
                    Driver Provider:"Intel Corporation"
                    Driver Version:"24.20.100.6286"
                    INF:"oem26.inf"
                    INF Section:"iKBLD_w10_DS"
                    Install Date:"Not Available"
                    Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\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_5926&SUBSYS_20688086&REV_06\3&11583659&0&10"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"Not Available"
                    Refresh Rate - Current:"60 Hz"
                    Refresh Rate - Maximum:"75 Hz"
                    Refresh Rate - Minimum:"50 Hz"
                    Resolution:"2560 X 1440"
                    Scan Mode:"Noninterlaced"
                    Service Name:"igfx"
                    Status:"OK"
                    Video Architecture:"VGA"
                    Video Memory:"Unknown"
                    Video Processor:"Intel(R) Iris(R) Graphics Family"
          - "Memory"
               Physical Memory (Available):"27.46 GB"
               Physical Memory (Installed):"32 GB"
               Physical Memory (Total):"31.89 GB"
               - "BANK 0"
                    Capacity:"16 GB"
                    Channel:"ChannelA-DIMM0"
                    Configured Clock Speed:"2133 MHz"
                    Configured Voltage:"1200 millivolts"
                    Data Width:"64 bits"
                    Form Factor:"SODIMM"
                    Interleave Position:"First position"
                    Manufacturer:"Micron"
                    Maximum Voltage:"Not Available"
                    Memory Type:"Unknown"
                    Minimum Voltage:"Not Available"
                    Part Number:"Not Available"
                    Serial Number:"00000124"
                    Status:"Not Available"
                    Type:"Not Available"
               - "BANK 2"
                    Capacity:"16 GB"
                    Channel:"ChannelB-DIMM0"
                    Configured Clock Speed:"2133 MHz"
                    Configured Voltage:"1200 millivolts"
                    Data Width:"64 bits"
                    Form Factor:"SODIMM"
                    Interleave Position:"Second position"
                    Manufacturer:"Micron"
                    Maximum Voltage:"Not Available"
                    Memory Type:"Unknown"
                    Minimum Voltage:"Not Available"
                    Part Number:"Not Available"
                    Serial Number:"00000124"
                    Status:"Not Available"
                    Type:"Not Available"
          - "Motherboard"
               Availability:"Running or Full Power"
               BIOS:"BNKBL357.86A.0088.2022.0125.1102, INTEL  - 58"
               Caption:"Motherboard"
               - "Chipset":"Intel(R)"
                    Link:"http://www.intel.com/content/www/us/en/search.html?keyword="
               Date:"01-24-2022 04:00 PM"
               Install Date:"Not Available"
               Last Error Code:"Not Available"
               Last Error Code Description:"Not Available"
               Manufacturer:"Intel Corporation"
               Model:"Not Available"
               Part Number:"Not Available"
               PNP Device ID:"Not Available"
               Power Management Capabilities:"Not Available"
               Power Management Supported:"Not Available"
               Product:"NUC7i5BNB"
               Serial Number:"GEBN90100VYN"
               Status:"OK"
               Version:"J31144-311"
          - "Networking"
               Intel ® Network Connections Install Options:"Not Available"
               Intel ® Network Connections Version:"Not Available"
               Intel ® PROSet/Wireless Software Version:"Not Available"
               - "Bluetooth Device (Personal Area Network)"
                    Availability:"Running or Full Power"
                    Caption:"Bluetooth Device (Personal Area Network)"
                    CoInstallers:"Not Available"
                    Default IP Gateway:"Not Available"
                    DHCP Enabled:"Yes"
                    DHCP Lease Expires:"Not Available"
                    DHCP Lease Obtained:"Not Available"
                    DHCP Server:"Not Available"
                    Driver:"bthpan.sys"
                    Driver Date:"06-21-2006 12:00 AM"
                    Driver Path:"C:\WINDOWS\system32\drivers\bthpan.sys"
                    Driver Provider:"Microsoft"
                    Driver Version:"10.0.19041.1"
                    Index:"0004"
                    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:"02-23-2022 03:25 PM"
                    Location:"Not Available"
                    MAC Address:"FC:77:74:BD:70:5D"
                    Manufacturer:"Microsoft"
                    Media Type:
                    Net Connection ID:"Bluetooth Network Connection"
                    NetCfgInstanceId:"{F22CAD03-D917-4E09-8598-B510522F1497}"
                    Number of VLANs:"0"
                    PNP Device ID:"BTH\MS_BTHPAN\6&1DFDDEB1&0&2"
                    Port:"Not Available"
                    Power Management (Low Power):"Not Available"
                    Power Management (Wake On LAN):"Not Available"
                    Power Management (Wake on Magic Packet):"Not Available"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Product Type:"Bluetooth Device (Personal Area Network)"
                    Service Name:"BthPan"
                    Status:"Enabled"
                    Team Name:"Not in a team"
                    Temperature:
                    Type:"Ethernet 802.3"
                    - "Service Bindings"
                         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:
               - "Intel(R) Dual Band Wireless-AC 8265"
                    Access Point:
                    Authentication:
                    Availability:"Running or Full Power"
                    - "Caption":"Intel(R) Dual Band Wireless-AC 8265"
                         Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Dual+Band+Wireless+AC+8265"
                    Channel:
                    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:"06-22-2021 12:00 AM"
                    Driver Path:"C:\WINDOWS\system32\drivers\Netwtw06.sys"
                    Driver Provider:"Intel"
                    Driver Version:"20.70.25.2"
                    Index:"0002"
                    INF:"oem73.inf"
                    INF Section:"Install_MPCIEX_GENSD_8265_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:"02-23-2022 03:25 PM"
                    Location:"PCI bus 58, device 0, function 0"
                    MAC Address:"FC:77:74:BD:70:59"
                    Manufacturer:"Intel Corporation"
                    Media Type:
                    Net Connection ID:"Wi-Fi"
                    NetCfgInstanceId:"{9FAF8C5B-8F80-475E-A11B-8BE5507B4769}"
                    Network Name:"Wi-Fi"
                    Network Type:
                    Number of VLANs:"0"
                    PNP Device ID:"PCI\VEN_8086&DEV_24FD&SUBSYS_90108086&REV_78\4&18747CB7&0&00E5"
                    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 8265"
                    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):
                         Link-Layer Topology Discovery Mapper I/O Driver:
                         Link-Layer Topology Discovery Responder:
                         Microsoft LLDP Protocol Driver:
                         Microsoft Network Monitor 3 Driver:
                         QoS Packet Scheduler:
                    - "Settings"
                         *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)"
                         *PacketCoalescing:Packet Coalescing:"Enabled (1)"
                         *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)"
                         *PMNSOffload:NS offload for WoWLAN:"Enabled (1)"
                         *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)"
                         *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)"
                         *WakeOnPattern:Wake on Pattern Match:"Enabled (1)"
                         ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)"
                         ChannelWidth52:Channel Width for 5GHz:"Auto (1)"
                         CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)"
                         FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)"
                         IbssTxPower:Transmit Power:"5. Highest (100)"
                         IEEE11nMode:802.11n/ac Wireless Mode:"802.11ac (2)"
                         MIMOPowerSaveMode:MIMO Power Save Mode:"Auto SMPS (0)"
                         RoamAggressiveness:Roaming Aggressiveness:"3. Medium (2)"
                         RoamingPreferredBandType:Preferred Band:"1. No Preference (0)"
                         ThroughputBoosterEnabled:Throughput Booster:"Disabled (0)"
                         uAPSDSupport:U-APSD support:"Disabled (0)"
                         WirelessMode:802.11a/b/g Wireless Mode:"6. Dual Band 802.11a/b/g (34)"
               - "Intel(R) Ethernet Connection (4) I219-V"
                    Availability:"Running or Full Power"
                    - "Caption":"Intel(R) Ethernet Connection (4) I219-V"
                         Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Ethernet+Connection+(4)+I219+V"
                    CoInstallers:"Not Available"
                    Default IP Gateway:"192.168.0.1;fe80::a204:60ff:fec0:f9b2"
                    DHCP Enabled:"Yes"
                    DHCP Lease Expires:"02-24-2022 03:25 PM"
                    DHCP Lease Obtained:"02-23-2022 03:25 PM"
                    DHCP Server:"192.168.0.1"
                    Driver:"e1d68x64.sys"
                    Driver Date:"05-07-2019 12:00 AM"
                    Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\e1d68x64.inf_amd64_546eef898d5d49f9\e1d68x64.sys"
                    Driver Provider:"Intel"
                    Driver Version:"12.18.9.7"
                    ETrackID:"Not Available"
                    Index:"0001"
                    INF:"oem66.inf"
                    INF Section:"E15D8.10.0.1"
                    Install Date:"Not Available"
                    Installed:"Yes"
                    IP Address:"192.168.0.28;fe80::206e:b1c:3ef6:d8ef;2603:8001:5843:ba00:6d94:2d1:c9b7:ffd9;2603:8001:5843:ba00:206e:b1c:3ef6:d8ef"
                    IP Subnet:"255.255.255.0;64;128;64"
                    Last Error Code:"Not Available"
                    Last Error Code Description:"Not Available"
                    Last Reset:"02-23-2022 03:25 PM"
                    Location:"PCI bus 0, device 31, function 6"
                    MAC Address:"94:C6:91:AC:70:C4"
                    Manufacturer:"Intel"
                    Media Type:
                    Net Connection ID:"Ethernet"
                    NetCfgInstanceId:"{25B30320-2A6D-4144-A135-E731744CCAFB}"
                    Number of VLANs:"0"
                    NVM Version:"Not Available"
                    Part Number:"FFFFFF-0FF"
                    PNP Device ID:"PCI\VEN_8086&DEV_15D8&SUBSYS_20688086&REV_21\3&11583659&0&FE"
                    Port:"Not Available"
                    Power Management (Low Power):"Active: Yes, Enable: Yes"
                    Power Management (Wake On LAN):"Active: Yes, Enable: Yes"
                    Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No"
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Product Type:"Intel(R) Ethernet Connection (4) I219-V"
                    Service Name:"e1dexpress"
                    Status:"Enabled"
                    Team Name:"Not in a team"
                    Temperature:
                    Type:"Ethernet 802.3"
                    - "Service Bindings"
                         Client for Microsoft Networks:
                         File and Printer Sharing for Microsoft Networks:
                         Internet Protocol Version 4 (TCP/IPv4):
                         Internet Protocol Version 6 (TCP/IPv6):
                         Link-Layer Topology Discovery Mapper I/O Driver:
                         Link-Layer Topology Discovery Responder:
                         Microsoft LLDP Protocol Driver:
                         Microsoft Network Monitor 3 Driver:
                         QoS Packet Scheduler:
                    - "Settings"
                         *FlowControl:Flow Control:"Rx & Tx Enabled (3)"
                         *InterruptModeration:Interrupt Moderation:"Enabled (1)"
                         *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)"
                         *JumboPacket:Jumbo Packet:"Disabled (1514)"
                         *LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)"
                         *LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)"
                         *NumRssQueues:Maximum Number of RSS Queues:"2 Queues (2)"
                         *PMARPOffload:Protocol ARP Offload:"Enabled (1)"
                         *PMNSOffload:Protocol NS Offload:"Enabled (1)"
                         *PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enabled (3)"
                         *PtpHardwareTimestamp:PTP Hardware Timestamp:"Disabled (0)"
                         *ReceiveBuffers:Receive Buffers:"256 (256)"
                         *RSS:Receive Side Scaling:"Enabled (1)"
                         *RSSProfile:RSS load balancing profile:"ClosestProcessor (1)"
                         *SoftwareTimestamp:Software Timestamp:"Disabled (0)"
                         *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)"
                         *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)"
                         *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)"
                         *TransmitBuffers:Transmit Buffers:"512 (512)"
                         *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)"
                         *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)"
                         *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)"
                         *WakeOnPattern:Wake on Pattern Match:"Enabled (1)"
                         AdaptiveIFS:Adaptive Inter-Frame Spacing:"Disabled (0)"
                         AutoPowerSaveModeEnabled:Link Speed Battery Saver:"Disabled (0)"
                         EEELinkAdvertisement:Energy Efficient Ethernet:"On (1)"
                         EnablePME:Enable PME:"Enabled (1)"
                         ITR:Interrupt Moderation Rate:"Adaptive (65535)"
                         LinkNegotiationProcess:Legacy Switch Compatibility Mode:"Disabled (1)"
                         LogLinkStateEvent:Log Link State Event:"Enabled (51)"
                         MasterSlave:Gigabit Master Slave Mode:"Auto Detect (0)"
                         ReduceSpeedOnPowerDown:Reduce Speed On Power Down:"Enabled (1)"
                         SipsEnabled:System Idle Power Saver:"Disabled (0)"
                         ULPMode:Ultra Low Power Mode:"Enabled (1)"
                         WaitAutoNegComplete:Wait for Link:"Auto Detect (2)"
                         WakeOnLink:Wake on Link Settings:"Disabled (0)"
          - "Operating System"
               .Net Framework Version:"4.0,4.8"
               Boot Device:"\Device\HarddiskVolume2"
               Locale:"United States"
               OS Manufacturer:"Microsoft Corporation"
               OS Name:"Microsoft Windows 10 Pro"
               Other OS Description:"Not Available"
               Page File:"C:\pagefile.sys"
               Page File Space:"4.75 GB"
               Physical Memory (Available):"27.47 GB"
               Physical Memory (Installed):"32 GB"
               Physical Memory (Total):"31.89 GB"
               System Directory:"C:\WINDOWS\system32"
               Version:"10.0.19044 Build 19044"
               Virtual Memory (Available):"32.17 GB"
               Virtual Memory (Total):"36.64 GB"
               Windows Directory:"C:\WINDOWS"
               - "Installed Updates"
                    KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]"
                    KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]"
                    KB4562830:"Update [12/26/2020]"
                    KB4577586:"Update [3/10/2021]"
                    KB4580325:"Security Update [12/26/2020]"
                    KB4589212:"Update [3/10/2021]"
                    KB4593175:"Security Update [12/26/2020]"
                    KB4598481:"Security Update [1/13/2021]"
                    KB5000736:"Update [5/20/2021]"
                    KB5003791:"Update [12/14/2021]"
                    KB5005699:"Security Update [9/15/2021]"
                    KB5006753:"Update [11/5/2021]"
                    KB5007273:"Update [12/14/2021]"
                    KB5009467:"Update [2/9/2022]"
                    KB5009636:"Update [1/28/2022]"
                    KB5010415:"Update [2/16/2022]"
                    KB5011352:"Security Update [2/9/2022]"
          - "Processor"
               - "Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz"
                    Architecture:"x64"
                    ATPO:"Not Available"
                    Availability:"Running or Full Power"
                    Caption:"Intel64 Family 6 Model 142 Stepping 9"
                    - "Chipset Name":"Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz"
                         Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i5+7260U+CPU+"
                    CPU Speed:"2.21 GHz"
                    Current Voltage:"8. volts"
                    Driver:"Not Available"
                    Driver Date:"04-21-2009 12:00 AM"
                    Driver Path:"C:\WINDOWS\system32\drivers\intelppm.sys"
                    Driver Provider:"Microsoft"
                    Driver Version:"10.0.19041.546"
                    Ext. Family:"Not Available"
                    Family:"Not Available"
                    FPO:"Not Available"
                    INF:"cpu.inf"
                    INF Section:"IntelPPM_Inst.NT"
                    Install Date:"Not Available"
                    Last Error Code:"Not Available"
                    Level 1 Cache:"2 x 128 KB"
                    Level 2 Cache:"2 x 512 KB"
                    Level 3 Cache:"4 MB"
                    Load:"71%"
                    Manufacturer:"GenuineIntel"
                    Model:"142"
                    Name:"Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz"
                    Number of Cores:"2"
                    Number of Cores Enabled:"2"
                    Number of Logical Processors:"4"
                    Part Number:"To Be Filled By O.E.M."
                    Power Management Capabilities:"Not Available"
                    Power Management Supported:"No"
                    Processor ID:"BFEBFBFF000806E9"
                    Revision:"Not Available"
                    Serial Number:"To Be Filled By O.E.M."
                    Service Name:"intelppm"
                    Status:"OK"
                    Stepping:"9"
                    Version:"Not Available"
          - "Storage"
               - "Intel Optane+298GBHDD"
                    Capablities:"Random Access, Supports Writing, SMART Notification"
                    - "Caption":"Intel Optane+298GBHDD"
                         Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Intel+Optane%2b298GBHDD"
                    Cylinder - Total:"38913"
                    Description:"Disk drive"
                    Driver:"Not Available"
                    Driver Date:"06-21-2006 12:00 AM"
                    Driver Version:"10.0.19041.789"
                    Error Code:"Device is working properly"
                    - "Firmware Revision":"18.30"
                         Link:"http://www.intel.com/content/www/us/en/support/solid-state-drives/000017245.html?wapkw=ssd+firmware"
                    Heads - Total:"255"
                    Index:"0"
                    INF:"disk.inf"
                    Install Date:"Not Available"
                    Interface Type:"SCSI"
                    Manufacturer:"(Standard disk drives)"
                    Model:"Intel Optane+298GBHDD"
                    Name:"\\.\PHYSICALDRIVE0"
                    Partitions:"7"
                    Physical Sector Size:"512"
                    PNP Device ID:"SCSI\DISK&VEN_INTEL&PROD_OPTANE+298GBHDD\4&39869D18&0&070000"
                    Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available"
                    SCSI Bus:"7"
                    SCSI LUN:"0"
                    SCSI Port:"0"
                    Sectors - Per Track:"63"
                    Sectors - Total:"625137345"
                    Serial Number:"Optane_0000"
                    Size:"298.09 GB"
                    Size – Available:"168.80 GB"
                    Status:"OK"
                    Tracks - Per Cylinder:"255"
                    Tracks - Total:"9922815"
                    - "C:"
                         Availability:"Not Available"
                         Caption:"C:"
                         Compression Method:"Not Compressed"
                         Description:"Local Fixed Disk"
                         File System:"NTFS"
                         Name:"NUC7I5BOOT"
                         Serial Number:"68C997EC"
                         Size:"147.19 GB"
                         Size – Available:"80.94 GB"
                         Status:"Not Available"
                         Volume Dirty:"No"
                    - "D:"
                         Availability:"Not Available"
                         Caption:"D:"
                         Compression Method:"Not Compressed"
                         Description:"Local Fixed Disk"
                         File System:"NTFS"
                         Name:"NUC7I5UserData01"
                         Serial Number:"DC80165A"
                         Size:"148.45 GB"
                         Size – Available:"87.79 GB"
                         Status:"Not Available"
                         Volume Dirty:"No"
...#SSU#...
#Logs#System Messages#Included
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The Group Policy Client service did not shut down properly after receiving a preshutdown control.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The name "NOABUSELIMITED :1d" could not be registered on the interface with IP address 192.168.0.28. The computer with the IP address 192.168.0.199 did not allow the name to be claimed by this computer.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The name "NOABUSELIMITED :1d" could not be registered on the interface with IP address 192.168.0.28. The computer with the IP address 192.168.0.199 did not allow the name to be claimed by this computer.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
DCOM got error "1068" attempting to start the service cdpsvc with arguments "Unavailable" in order to run the server:
{284CACFE-B6F2-461A-90C3-A7ACC8353816}
-------------------------------------------------------------------
The CDPSvc service depends on the NcbService service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The NcbService service terminated with the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 name "NOABUSELIMITED :1d" could not be registered on the interface with IP address 192.168.0.28. The computer with the IP address 192.168.0.199 did not allow the name to be claimed by this computer.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 name "NOABUSELIMITED :1d" could not be registered on the interface with IP address 192.168.0.28. The computer with the IP address 192.168.0.199 did not allow the name to be claimed by this computer.
-------------------------------------------------------------------
The name "NOABUSELIMITED :1d" could not be registered on the interface with IP address 192.168.0.28. The computer with the IP address 192.168.0.199 did not allow the name to be claimed by this computer.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 name "NOABUSELIMITED :1d" could not be registered on the interface with IP address 192.168.0.28. The computer with the IP address 192.168.0.199 did not allow the name to be claimed by this computer.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The Group Policy Client service did not shut down properly after receiving a preshutdown control.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
 ID: 7872
 Source: System.ServiceModel.Activation.TcpWorkerProcess/9786932
 Exception: System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

Server stack trace: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
  Process Name: SMSvcHost
 Process ID: 3676

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x8024001E: Windows Malicious Software Removal Tool x64 - v5.94 (KB890830).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
 ID: 13908
 Source: System.ServiceModel.Activation.TcpWorkerProcess/8294013
 Exception: System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

Server stack trace: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
  Process Name: SMSvcHost
 Process ID: 3844

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 4:54:06 AM on ‎9/‎11/‎2021 was unexpected.
-------------------------------------------------------------------
Windows failed fast startup with error status 0xC00000D4.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The name "NOABUSELIMITED :1d" could not be registered on the interface with IP address 192.168.0.28. The computer with the IP address 192.168.0.199 did not allow the name to be claimed by this computer.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The Energy Server Service queencreek service terminated unexpectedly.  It has done this 1 time(s).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
The network address is invalid. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Bluetooth User Support Service_171bd95 service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 500 milliseconds: Restart the service.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 the underlying transport for 127.0.0.1:50003. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50002. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50001. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
 ID: 13280
 Source: System.ServiceModel.Activation.TcpWorkerProcess/24581054
 Exception: System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

Server stack trace: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
  Process Name: SMSvcHost
 Process ID: 4068

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Bluetooth User Support Service_513d3f service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 500 milliseconds: Restart the service.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 the underlying transport for 127.0.0.1:50001. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
 ID: 5548
 Source: System.ServiceModel.Activation.TcpWorkerProcess/28106152
 Exception: System.ServiceModel.ServiceActivationException: An error occurred while duplicating a socket. See inner exception for more information. ---> System.Net.Sockets.SocketException: An invalid argument was supplied
   at System.Net.Sockets.Socket.DuplicateAndClose(Int32 targetProcessId)
   at System.ServiceModel.Channels.SocketConnection.DuplicateAndClose(Int32 targetProcessId)
   at System.ServiceModel.Activation.TcpWorkerProcess.DuplicateConnection(ListenerSessionConnection session)
   --- End of inner exception stack trace ---
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
  Process Name: SMSvcHost
 Process ID: 3552

-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x8024200B: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.343.113.0).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 11:36:11 AM on ‎6/‎9/‎2021 was unexpected.
-------------------------------------------------------------------
Windows failed fast startup with error status 0xC00000D4.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x8024200B: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.341.40.0).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
 ID: 9544
 Source: System.ServiceModel.Activation.TcpWorkerProcess/10959549
 Exception: System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

Server stack trace: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
  Process Name: SMSvcHost
 Process ID: 3916

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The following service has repeatedly stopped responding to service control requests: Microsoft Defender Antivirus Service

Contact the service vendor or the system administrator about whether to disable this service until the problem is identified.

You may have to restart the computer in safe mode before you can disable the service.
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service.
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service.
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service.
-------------------------------------------------------------------
The Energy Server Service queencreek service terminated unexpectedly.  It has done this 1 time(s).
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 WinDefend service.
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service.
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
 ID: 11440
 Source: System.ServiceModel.Activation.TcpWorkerProcess/39802291
 Exception: System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

Server stack trace: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
  Process Name: SMSvcHost
 Process ID: 3780

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50001. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x8024200B: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.339.278.0).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.423_neutral_neutral_cw5n1h2txyewy!Windows.Networking.BackgroundTransfer.Internal.NetworkChangeTask.ClassId.1 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 processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x8024200B: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.337.129.0).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.423_neutral_neutral_cw5n1h2txyewy!App.AppX447jn8wbjb1qsw3jxkndb19cwgsrtrkk.mca did not register with DCOM within the required timeout.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 the underlying transport for 127.0.0.1:50559. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50558. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50557. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50556. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50555. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50554. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50553. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50552. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50551. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50550. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50549. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50548. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50547. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50546. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50545. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50544. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50543. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50542. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50541. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50540. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50539. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50538. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50537. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50536. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50535. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50534. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50533. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50532. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50531. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50530. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50529. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50528. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50527. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50526. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50525. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50524. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50523. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50522. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50521. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50520. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50519. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50518. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50517. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50516. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50515. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50514. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50513. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50512. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50511. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50510. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50509. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50508. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50507. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50506. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50505. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50504. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50503. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50502. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50501. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50500. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50499. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50498. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50497. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50496. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50495. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50494. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50493. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50492. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50491. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50490. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50489. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50488. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50487. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50486. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50485. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50484. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50483. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50482. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50481. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50480. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50479. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50478. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50477. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50476. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50475. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50474. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50473. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50472. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50471. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50470. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50469. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50468. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50467. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50466. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50465. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50464. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50463. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50462. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50461. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50460. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50459. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50458. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50457. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50456. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50455. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50454. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50453. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50452. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50451. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50450. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50449. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50448. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50447. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50446. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50445. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50444. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50443. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50442. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50441. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50440. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50439. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50438. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50437. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50436. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50435. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50434. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50433. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50432. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50431. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50430. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50429. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50428. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50427. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50426. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50425. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50424. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50423. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50422. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50421. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50420. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50419. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50418. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50417. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50416. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50415. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50414. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50413. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50412. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50411. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50410. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50409. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50408. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50407. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50406. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50405. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50404. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50403. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50402. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50401. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50400. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50399. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50398. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50397. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50396. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50395. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50394. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50393. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50392. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50391. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50390. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50389. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50388. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50387. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50386. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50385. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50384. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50383. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50382. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50381. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50380. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50379. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50378. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50377. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50376. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50375. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50374. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50373. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50372. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50371. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50370. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50369. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50368. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50367. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50366. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50365. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50364. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50363. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50362. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50361. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50360. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50359. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50358. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50357. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50356. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50355. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50354. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50353. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50352. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50351. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50350. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50349. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50348. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50347. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50346. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50345. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50344. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50343. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50342. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50341. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50340. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50339. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50338. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50337. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50336. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50335. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50334. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50333. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50332. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50331. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50330. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50329. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50328. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50327. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50326. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50325. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50324. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50323. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50322. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50321. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50320. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50319. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50318. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50317. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50316. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50315. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50314. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50313. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50312. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50311. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50310. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50309. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50308. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50307. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50306. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50305. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50304. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50303. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50302. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50301. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50300. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50299. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50298. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50297. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50296. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50295. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50294. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50293. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50292. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50291. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50290. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50289. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50288. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50287. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50286. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50285. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50284. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50283. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50282. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50281. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50280. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50279. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50278. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50277. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50276. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50275. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50274. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50273. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50272. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50271. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50270. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50269. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50268. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50267. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50266. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50265. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50264. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50263. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50262. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50261. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50260. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50259. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50258. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50257. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50256. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50255. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50254. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50253. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50252. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50251. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50250. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50249. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50248. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50247. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50246. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50245. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50244. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50243. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50242. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50241. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50240. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50239. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50238. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50237. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50236. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50235. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50234. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50233. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50232. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50231. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50230. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50229. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50228. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50227. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50226. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50225. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50224. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50223. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50222. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50221. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50220. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50219. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50218. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50217. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50216. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50215. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50214. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50213. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50212. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50211. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50210. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50209. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50208. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50207. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50206. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50205. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50204. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50203. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50202. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50201. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50200. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50199. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50198. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50197. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50196. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50195. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50194. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50193. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50192. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50191. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50190. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50189. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50188. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50187. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50186. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50185. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50184. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50183. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50182. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50181. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50180. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50179. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50178. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50177. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50176. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50175. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50174. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50173. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50172. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50171. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50170. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50169. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50168. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50167. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50166. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50165. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50164. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50163. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50162. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50161. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50160. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50159. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50158. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50157. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50156. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50155. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50154. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50153. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50152. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50151. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50150. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50149. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50148. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50147. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50146. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50145. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50144. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50143. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50142. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50141. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50140. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50139. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50138. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50137. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50136. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50135. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50134. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50133. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50132. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50131. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50130. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50129. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50128. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50127. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50126. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50125. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50124. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50123. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50122. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50121. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50120. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50119. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50118. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50117. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50116. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50115. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50114. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50113. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50112. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50111. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50110. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50109. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50108. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50107. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50106. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50105. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50104. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50103. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50102. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50101. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50100. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50099. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50098. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50097. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50096. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50095. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50094. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50093. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50092. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50091. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50090. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50089. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50088. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50087. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50086. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50085. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50084. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50083. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50082. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50081. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50080. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50079. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50078. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50077. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50076. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50075. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50074. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50073. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50072. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50071. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50070. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50069. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50068. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50067. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50066. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50065. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50064. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50063. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50062. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50061. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50060. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50059. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50058. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50057. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50056. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50055. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50054. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50053. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50052. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50051. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50050. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50049. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50048. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50047. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50046. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50045. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50044. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50043. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50042. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50041. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50040. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50039. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50038. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50037. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50036. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50035. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50034. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50033. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50032. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50031. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50030. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50029. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50028. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50027. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50026. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50025. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50024. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50023. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50022. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50021. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50020. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50019. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50018. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50017. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50016. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50015. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50014. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50013. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50012. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50011. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50010. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50009. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50008. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50007. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50006. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50005. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50004. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50003. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50002. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50001. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The NcbService service terminated with the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 5:48:32 AM on ‎4/‎24/‎2021 was unexpected.
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50159. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50158. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50157. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50156. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50155. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50154. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50153. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50152. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50151. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50150. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50149. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50148. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50147. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50146. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50145. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50144. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50143. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50142. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50141. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50140. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50139. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50138. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50137. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50136. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50135. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50134. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50133. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50132. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50131. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50130. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50129. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50128. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50127. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50126. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50125. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50124. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50123. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50122. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50121. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50120. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50119. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50118. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50117. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50116. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50115. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50114. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50113. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50112. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50111. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50110. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50109. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50108. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50107. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50106. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50105. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50104. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50103. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50102. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50101. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50100. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50099. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50098. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50097. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50096. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50095. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50094. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50093. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50092. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50091. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50090. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50089. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50088. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50087. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50086. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50085. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50084. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50083. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50082. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50081. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50080. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50079. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50078. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50077. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50076. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50075. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50074. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50073. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50072. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50071. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50070. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50069. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50068. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50067. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50066. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50065. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50064. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50063. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50062. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50061. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50060. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50059. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50058. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50057. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50056. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50055. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50054. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50053. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50052. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50051. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50050. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50049. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50048. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50047. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50046. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50045. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50044. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50043. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50042. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50041. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50040. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50039. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50038. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50037. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50036. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50035. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50034. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50033. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50032. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50031. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50030. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50029. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50028. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50027. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50026. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50025. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50024. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50023. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50022. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50021. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50020. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50019. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50018. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50017. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50016. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50015. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50014. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50013. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50012. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50011. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50010. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50009. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50008. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50007. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50006. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50005. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50004. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50003. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50002. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50001. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50459. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50458. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50457. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50456. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50455. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50454. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50453. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50452. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50451. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50450. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50449. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50448. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50447. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50446. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50445. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50444. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50443. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50442. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50441. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50440. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50439. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50438. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50437. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50436. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50435. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50434. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50433. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50432. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50431. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50430. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50429. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50428. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50427. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50426. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50425. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50424. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50423. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50422. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50421. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50420. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50419. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50418. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50417. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50416. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50415. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50414. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50413. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50412. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50411. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50410. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50409. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50408. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50407. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50406. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50405. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50404. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50403. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50402. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50401. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50400. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50399. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50398. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50397. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50396. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50395. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50394. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50393. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50392. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50391. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50390. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50389. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50388. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50387. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50386. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50385. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50384. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50383. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50382. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50381. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50380. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50379. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50378. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50377. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50376. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50375. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50374. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50373. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50372. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50371. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50370. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50369. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50368. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50367. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50366. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50365. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50364. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50363. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50362. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50361. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50360. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50359. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50358. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50357. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50356. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50355. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50354. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50353. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50352. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50351. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50350. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50349. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50348. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50347. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50346. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50345. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50344. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50343. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50342. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50341. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50340. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50339. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50338. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50337. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50336. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50335. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50334. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50333. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50332. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50331. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50330. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50329. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50328. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50327. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50326. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50325. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50324. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50323. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50322. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50321. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50320. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50319. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50318. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50317. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50316. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50315. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50314. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50313. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50312. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50311. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50310. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50309. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50308. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50307. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50306. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50305. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50304. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50303. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50302. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50301. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50300. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50299. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50298. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50297. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50296. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50295. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50294. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50293. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50292. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50291. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50290. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50289. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50288. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50287. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50286. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50285. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50284. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50283. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50282. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50281. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50280. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50279. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50278. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50277. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50276. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50275. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50274. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50273. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50272. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50271. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50270. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50269. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50268. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50267. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50266. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50265. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50264. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50263. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50262. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50261. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50260. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50259. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50258. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50257. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50256. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50255. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50254. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50253. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50252. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50251. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50250. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50249. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50248. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50247. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50246. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50245. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50244. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50243. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50242. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50241. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50240. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50239. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50238. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50237. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50236. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50235. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50234. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50233. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50232. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50231. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50230. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50229. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50228. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50227. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50226. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50225. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50224. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50223. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50222. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50221. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50220. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50219. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50218. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50217. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50216. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50215. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50214. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50213. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50212. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50211. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50210. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50209. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50208. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50207. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50206. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50205. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50204. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50203. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50202. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50201. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50200. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50199. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50198. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50197. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50196. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50195. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50194. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50193. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50192. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50191. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50190. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50189. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50188. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50187. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50186. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50185. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50184. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50183. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50182. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50181. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50180. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50179. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50178. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50177. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50176. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50175. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50174. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50173. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50172. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50171. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50170. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50169. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50168. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50167. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50166. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50165. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50164. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50163. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50162. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50161. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50160. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50159. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50158. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50157. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50156. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50155. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50154. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50153. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50152. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50151. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50150. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50149. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50148. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50147. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50146. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50145. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50144. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50143. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50142. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50141. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50140. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50139. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50138. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50137. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50136. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50135. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50134. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50133. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50132. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50131. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50130. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50129. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50128. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50127. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50126. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50125. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50124. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50123. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50122. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50121. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50120. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50119. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50118. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50117. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50116. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50115. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50114. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50113. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50112. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50111. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50110. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50109. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50108. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50107. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50106. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50105. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50104. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50103. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50102. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50101. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50100. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50099. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50098. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50097. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50096. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50095. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50094. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50093. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50092. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50091. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50090. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50089. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50088. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50087. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50086. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50085. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50084. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50083. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50082. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50081. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50080. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50079. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50078. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50077. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50076. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50075. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50074. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50073. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50072. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50071. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50070. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50069. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50068. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50067. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50066. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50065. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50064. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50063. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50062. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50061. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50060. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50059. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50058. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50057. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50056. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50055. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50054. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50053. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50052. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50051. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50050. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50049. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50048. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50047. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50046. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50045. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50044. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50043. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50042. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50041. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50040. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50039. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50038. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50037. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50036. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50035. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50034. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50033. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50032. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50031. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50030. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50029. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50028. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50027. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50026. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50025. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50024. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50023. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50022. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50021. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50020. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50019. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50018. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50017. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50016. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50015. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50014. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50013. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50012. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50011. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50010. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50009. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50008. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50007. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50006. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50005. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50004. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50003. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50002. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50001. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
The System Guard Runtime Monitor Broker service hung on starting.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The Downloaded Maps Manager service hung on starting.
-------------------------------------------------------------------
The File History Service service hung on starting.
-------------------------------------------------------------------
The Delivery Optimization service hung on starting.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
Windows failed fast startup with error status 0xC00000D4.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 the underlying transport for 127.0.0.1:50059. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50058. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50057. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50056. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50055. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50054. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50053. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50052. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50051. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50050. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50049. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50048. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50047. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50046. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50045. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50044. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50043. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50042. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50041. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50040. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50039. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50038. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50037. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50036. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50035. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50034. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50033. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50032. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50031. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50030. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50029. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50028. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50027. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50026. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50025. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50024. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50023. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50022. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50021. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50020. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50019. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50018. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50017. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50016. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50015. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50014. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50013. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50012. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50011. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50010. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50009. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50008. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50007. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50006. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50005. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50004. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50003. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50002. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50001. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The VMSP service failed to start due to the following error: 
Insufficient system resources exist to complete the requested service.
-------------------------------------------------------------------
The hns service depends on the VfpExt service which failed to start because of the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 the underlying transport for 127.0.0.1:50001. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The NcbService service terminated with the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service UsoSvc with arguments "Unavailable" in order to run the server:
{9C695035-48D2-4229-8B73-4C70E756E519}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server:
{E60687F7-01A1-40AA-86AC-DB1CBF673334}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The previous system shutdown at 5:39:08 AM on ‎2/‎8/‎2021 was unexpected.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 1:52:49 AM on ‎1/‎17/‎2021 was unexpected.
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
 ID: 10288
 Source: System.ServiceModel.Activation.TcpWorkerProcess/24729763
 Exception: System.ServiceModel.CommunicationException: The server did not provide a meaningful reply; this might be caused by a contract mismatch, a premature session shutdown or an internal server error.

Server stack trace: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeEndService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Activation.WorkerProcess.EndDispatchSession(IAsyncResult result)
  Process Name: SMSvcHost
 Process ID: 3968

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

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

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Function Discovery Resource Publication service terminated with the following error: 
The requested address is not valid in its context.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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:45:41 AM on ‎12/‎30/‎2020 was unexpected.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The cpuz139 service failed to start due to the following error: 
This driver has been blocked from loading
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The Intel(R) Storage Middleware Service service terminated unexpectedly.  It has done this 1 time(s).
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Intel(R) Storage Middleware Service service terminated unexpectedly.  It has done this 1 time(s).
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
The Intel(R) Storage Middleware Service service terminated unexpectedly.  It has done this 1 time(s).
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 Peer Name Resolution Protocol service terminated with the following error: 
Unable to access a key.
-------------------------------------------------------------------
The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with error code: 0x80630203.
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
The Intel(R) Storage Middleware Service service terminated unexpectedly.  It has done this 1 time(s).
-------------------------------------------------------------------
The Windows Server Essentials Client Computer Monitoring Service service terminated with the following error: 
Incorrect function.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
The cpuz139 service failed to start due to the following error: 
This driver has been blocked from loading
-------------------------------------------------------------------
The cpuz139 service failed to start due to the following error: 
This driver has been blocked from loading
-------------------------------------------------------------------
The cpuz139 service failed to start due to the following error: 
This driver has been blocked from loading
-------------------------------------------------------------------
Not Available
-------------------------------------------------------------------
The Peer Name Resolution Protocol service terminated with the following error: 
Unable to access a key.
-------------------------------------------------------------------
The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with error code: 0x80630203.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 9:16:00 AM on ‎12/‎28/‎2020 was unexpected.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
-------------------------------------------------------------------
The previous system shutdown at 8:19:26 AM on ‎12/‎28/‎2020 was unexpected.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to 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 start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary 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 user 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 obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the user 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 obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the user 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 obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the user 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 obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the user 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 obtain the name of a domain controller. This could be caused by a name resolution failure. Verify your Domain Name System (DNS) is configured and working correctly.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
This computer was not able to set up a secure session with a domain controller in domain NOABUSELIMITED due to the following: 
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. 
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

ADDITIONAL INFO 
If this computer is a domain controller for the specified domain, it sets up the secure session to the 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 was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The processing of Group Policy failed. Windows could not resolve the user 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 could not authenticate with \\DELLT340.NOABUSELIMITED.local, a Windows domain controller for domain NOABUSELIMITED, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator.
-------------------------------------------------------------------
The User Energy Server Service queencreek service terminated with the following error: 
Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000).
-------------------------------------------------------------------
Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule {59acfbf6-079c-434b-b26a-0f8c59114ef7} failed with error 0x57
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
Unable to start a DCOM Server: Microsoft.Windows.Cortana_1.10.7.17134_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppXynb3eakad12451rv00qxextfnce9sxb8.mca as Unavailable/Unavailable. The error:
"2147942667"
Happened while starting this command:
"C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe" -ServerName:CortanaUI.AppXa50dqqa5gqv4a428c9y1jjw7m3btvepj.mca
-------------------------------------------------------------------
Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error:
"2147942767"
Happened while starting this command:
C:\WINDOWS\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}
-------------------------------------------------------------------
The Peer Name Resolution Protocol service terminated with the following error: 
Unable to access a key.
-------------------------------------------------------------------
The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with error code: 0x80630203.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50006. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50005. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50004. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50003. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50002. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
Unable to bind to the underlying transport for 127.0.0.1:50001. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control.
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server:
{752073A1-23F2-4396-85F0-8FDB879ED0ED}
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
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 RmSvc with arguments "Unavailable" in order to run the server:
{581333F6-28DB-41BE-BC7A-FF201F12F3F6}
-------------------------------------------------------------------
DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server:
{A47979D2-C419-11D9-A5B4-001185AD2B89}
-------------------------------------------------------------------
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 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 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 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 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 Dnscache service depends on the AFD 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 DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server:
DispBrokerDesktop.GlobalBrokerInstance
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.
-------------------------------------------------------------------
Unable to initialize the security package Basic for server side authentication.  The data field contains the error number.
-------------------------------------------------------------------
Unable to initialize the security package Negotiate for server side authentication.  The data field contains the error number.
-------------------------------------------------------------------
Unable to initialize the security package NTLM for server side authentication.  The data field contains the error number.
-------------------------------------------------------------------
Unable to initialize the security package WDigest for server side authentication.  The data field contains the error number.
-------------------------------------------------------------------
The Network Connection Broker service terminated with the following error: 
A device attached to the system is not functioning.
-------------------------------------------------------------------
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Network List Service service terminated with the following error: 
The device is not ready.
-------------------------------------------------------------------
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Network List Service service terminated with the following error: 
The device is not ready.
-------------------------------------------------------------------
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
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 Network List Service service terminated with the following error: 
The device is not ready.
...#SSU#...
#Logs#Direct-X Diagnostics#Included
------------------
System Information
------------------
      Time of this report: 2/23/2022, 15:29:00
             Machine name: NUC7I5BN
               Machine Id: {0B727DC1-CBEF-4808-86EA-90BA1D28199C}
         Operating System: Windows 10 Pro 64-bit (10.0, Build 19044) (19041.vb_release.191206-1406)
                 Language: English (Regional Setting: English)
      System Manufacturer: Intel(R) Client Systems
             System Model: NUC7i5BNH
                     BIOS: BNKBL357.86A.0088.2022.0125.1102 (type: UEFI)
                Processor: Intel(R) Core(TM) i5-7260U CPU @ 2.20GHz (4 CPUs), ~2.2GHz
                   Memory: 32768MB RAM
      Available OS Memory: 32652MB RAM
                Page File: 4617MB used, 32899MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 96 DPI (100 percent)
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
 DirectX Database Version: 1.0.8
           DxDiag Version: 10.00.19041.0928 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: 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) Iris(R) Plus Graphics 640
        Manufacturer: Intel Corporation
           Chip type: Intel(R) Iris(R) Graphics Family
            DAC type: Internal
         Device Type: Full Device (POST)
          Device Key: Enum\PCI\VEN_8086&DEV_5926&SUBSYS_20688086&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: 16454 MB
    Dedicated Memory: 128 MB
       Shared Memory: 16326 MB
        Current Mode: 2560 x 1440 (32 bit) (60Hz)
         HDR Support: Not Supported
    Display Topology: Internal
 Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
     Color Primaries: Red(0.654297,0.333008), Green(0.304688,0.625977), Blue(0.146484,0.046875), White Point(0.313477,0.329102)
   Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
        Monitor Name: Generic PnP Monitor
       Monitor Model: PB328
          Monitor Id: ACI32A5
         Native Mode: 2560 x 1440(p) (59.951Hz)
         Output Type: HDMI
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_9af403f73c0e9f69\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd12umd64.dll
 Driver File Version: 24.20.0100.6286 (English)
      Driver Version: 24.20.100.6286
         DDI Version: 12
      Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
        Driver Model: WDDM 2.4
 Hardware Scheduling: Supported:False Enabled:False 
 Graphics Preemption: Triangle
  Compute Preemption: Thread
            Miracast: Supported
      Detachable GPU: No
 Hybrid Graphics GPU: Integrated
      Power P-states: Not Supported
      Virtualization: Paravirtualization 
          Block List: DISABLE_HWSCH
  Catalog Attributes: Universal:False Declarative:False 
   Driver Attributes: Final Retail
    Driver Date/Size: 2018-08-14 16:00:00, 2019736 bytes
         WHQL Logo'd: Yes
     WHQL Date Stamp: Unknown
   Device Identifier: {D7B78E66-1A66-11CF-B8FB-0C00BDC2D535}
           Vendor ID: 0x8086
           Device ID: 0x5926
           SubSys ID: 0x20688086
         Revision ID: 0x0006
  Driver Strong Name: oem26.inf:5f63e534fc3bd056:iKBLD_w10_DS:24.20.100.6286:pci\ven_8086&dev_5926&subsys_20688086
      Rank Of Driver: 00D10001
         Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C 
         DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeMPEG2_IDCT  DXVA2_ModeVC1_D2010  {E07EC519-E651-4CD6-AC84-1370CCEEC851}  {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89}  DXVA2_ModeWMV9_IDCT  DXVA2_ModeVC1_IDCT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_Multiview_NoFGT  {C528916C-C0AF-4645-8CB2-372B6D4ADC2A}  {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A}  DXVA2_ModeVP8_VLD  {442B942A-B4D9-4940-BC45-A882E5F919F3}  {97688186-56A8-4094-B543-FC9DAAA49F4B}  {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B}  {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27}  {FFC79924-5EAF-4666-A736-06190F281443}  {F416F7BD-098A-4CF1-A11B-CE54959CA03D}  {BF44DACD-217F-4370-A383-D573BC56707E}  {2364D06A-F67F-4186-AED0-62B99E1784F1}  {464BDB3C-91C4-4E9B-896F-225496AC4ED6}  {28566328-F041-4466-8B14-8F5831E78F8B}  {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600}  {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2}  DXVA2_ModeHEVC_VLD_Main  {75FC75F7-C589-4A07-A25B-72E03B0383B3}  DXVA2_ModeHEVC_VLD_Main10  {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA}  DXVA2_ModeVP9_VLD_Profile0  DXVA2_ModeVP9_VLD_10bit_Profile2  {76988A52-DF13-419A-8E64-FFCF4A336CF5}  {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8}  {8DE911C4-C898-4364-9715-1DE6B3FE773D}  {50925B7B-E931-4978-A12A-586630F095F9}  {49761BEC-4B63-4349-A5FF-87FFDF088466}  
   Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 
                     {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering 
                     {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch 
                     {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend 
        D3D9 Overlay: Supported
             DXVA-HD: Supported
        DDraw Status: Enabled
          D3D Status: Enabled
          AGP Status: Enabled
       MPO MaxPlanes: 3
            MPO Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3)
         MPO Stretch: 5.000X - 0.334X
     MPO Media Hints: colorspace Conversion 
         MPO Formats: NV12,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM
    PanelFitter Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3)
 PanelFitter Stretch: 5.000X - 0.334X

-------------
Sound Devices
-------------
            Description: PB328 (Intel(R) Display Audio)
 Default Sound Playback: No
 Default Voice Playback: No
            Hardware ID: INTELAUDIO\FUNC_01&VEN_8086&DEV_280B&SUBSYS_80860101&REV_1000
        Manufacturer ID: N/A
             Product ID: N/A
                   Type: N/A
            Driver Name: IntcDAud.sys
         Driver Version: 10.25.0.10 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 2018-07-17 16:00:00, 635192 bytes
            Other Files: 
        Driver Provider: Intel(R) Corporation
         HW Accel Level: Emulation Only
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

            Description: Speakers (Realtek(R) Audio)
 Default Sound Playback: Yes
 Default Voice Playback: Yes
            Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0283&SUBSYS_80862068&REV_1000
        Manufacturer ID: N/A
             Product ID: N/A
                   Type: N/A
            Driver Name: RTKVHD64.sys
         Driver Version: 6.0.8716.1 (English)
      Driver Attributes: Final Retail
            WHQL Logo'd: Yes
          Date and Size: 2019-05-27 16:00:00, 6871640 bytes
            Other Files: 
        Driver Provider: Realtek Semiconductor Corp.
         HW Accel Level: Emulation Only
              Cap Flags: 0xF1F
    Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
 Static/Strm HW 3D Bufs: 0, 0
              HW Memory: 0
       Voice Management: No
 EAX(tm) 2.0 Listen/Src: No, No
   I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

---------------------
Sound Capture Devices
---------------------
            Description: Microphone (Realtek(R) Audio)
  Default Sound Capture: Yes
  Default Voice Capture: Yes
            Driver Name: RTKVHD64.sys
         Driver Version: 6.0.8716.1 (English)
      Driver Attributes: Final Retail
          Date and Size: 2019-05-27 16:00:00, 6871640 bytes
              Cap Flags: 0x1
           Format Flags: 0xFFFFF

            Description: Microphone Array (Realtek(R) Audio)
  Default Sound Capture: No
  Default Voice Capture: No
            Driver Name: RTKVHD64.sys
         Driver Version: 6.0.8716.1 (English)
      Driver Attributes: Final Retail
          Date and Size: 2019-05-27 16:00:00, 6871640 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

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub (USB 3.0)
| Vendor/Product ID: 0x8086, 0x9D2F
| Matching Device ID: USB\ROOT_HUB30
| Service: USBHUB3
| Driver: USBHUB3.SYS, 9/15/2021 02:20:34, 648016 bytes
| 
+-+ Generic USB Hub
| | Vendor/Product ID: 0x0409, 0x005A
| | Location: Port_#0003.Hub_#0001
| | Matching Device ID: USB\USB20_HUB
| | Service: USBHUB3
| | Driver: USBHUB3.SYS, 9/15/2021 02:20:34, 648016 bytes
| | 
| +-+ USB Input Device
| | | Vendor/Product ID: 0x046D, 0xC408
| | | Location: Port_#0003.Hub_#0002
| | | Matching Device ID: USB\Class_03&SubClass_01
| | | Service: HidUsb
| | | Driver: hidusb.sys, 4/14/2021 02:06:47, 44032 bytes
| | | Driver: hidclass.sys, 4/14/2021 02:06:47, 225792 bytes
| | | Driver: hidparse.sys, 4/14/2021 02:06:47, 46080 bytes
| | | 
| | +-+ Logitech HID-compliant Marble Mouse
| | | | Vendor/Product ID: 0x046D, 0xC408
| | | | Matching Device ID: hid\vid_046d&pid_c408
| | | | Upper Filters: LMouFilt
| | | | Lower Filters: LHidFilt
| | | | Service: mouhid
| | | | Driver: LHidFilt.Sys, 10/24/2020 23:32:28, 63552 bytes
| | | | Driver: LMouFilt.Sys, 10/24/2020 23:32:30, 54336 bytes
| | | | Driver: mouhid.sys, 12/7/2019 01:07:56, 35328 bytes
| | | | Driver: mouclass.sys, 12/7/2019 01:07:56, 67600 bytes
| | | | Driver: LkmdfCoInst.dll, 10/24/2020 23:32:30, 1980992 bytes
| | | | Driver: LMouFiltCoInst.dll, 10/24/2020 23:32:32, 113216 bytes
| | | 
| +-+ Generic USB Hub
| | | Vendor/Product ID: 0x0557, 0x8021
| | | Location: Port_#0004.Hub_#0002
| | | Matching Device ID: USB\USB20_HUB
| | | Service: USBHUB3
| | | Driver: USBHUB3.SYS, 9/15/2021 02:20:34, 648016 bytes
| | | 
| | +-+ USB Composite Device
| | | | Vendor/Product ID: 0x0557, 0x2288
| | | | Location: Port_#0001.Hub_#0003
| | | | Matching Device ID: USB\COMPOSITE
| | | | Service: usbccgp
| | | | Driver: usbccgp.sys, 12/26/2020 13:26:58, 185664 bytes
| | | | 
| | | +-+ USB Input Device
| | | | | Vendor/Product ID: 0x0557, 0x2288
| | | | | Location: 0000.0014.0000.003.004.001.000.000.000
| | | | | Matching Device ID: USB\Class_03&SubClass_01
| | | | | Service: HidUsb
| | | | | Driver: hidusb.sys, 4/14/2021 02:06:47, 44032 bytes
| | | | | Driver: hidclass.sys, 4/14/2021 02:06:47, 225792 bytes
| | | | | Driver: hidparse.sys, 4/14/2021 02:06:47, 46080 bytes
| | | | | 
| | | | +-+ HID Keyboard Device
| | | | | | Vendor/Product ID: 0x0557, 0x2288
| | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
| | | | | | Service: kbdhid
| | | | | | Driver: kbdhid.sys, 12/7/2019 01:07:56, 46592 bytes
| | | | | | Driver: kbdclass.sys, 12/7/2019 01:07:56, 71480 bytes
| | | | | 
| | | +-+ USB Input Device
| | | | | Vendor/Product ID: 0x0557, 0x2288
| | | | | Location: 0000.0014.0000.003.004.001.000.000.000
| | | | | Matching Device ID: USB\Class_03&SubClass_01
| | | | | Service: HidUsb
| | | | | Driver: hidusb.sys, 4/14/2021 02:06:47, 44032 bytes
| | | | | Driver: hidclass.sys, 4/14/2021 02:06:47, 225792 bytes
| | | | | Driver: hidparse.sys, 4/14/2021 02:06:47, 46080 bytes
| | | | | 
| | | | +-+ HID-compliant mouse
| | | | | | Vendor/Product ID: 0x0557, 0x2288
| | | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE
| | | | | | Service: mouhid
| | | | | | Driver: mouhid.sys, 12/7/2019 01:07:56, 35328 bytes
| | | | | | Driver: mouclass.sys, 12/7/2019 01:07:56, 67600 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 82.9 GB
Total Space: 150.7 GB
File System: NTFS
      Model: Intel Optane+298GBHDD

      Drive: D:
 Free Space: 89.9 GB
Total Space: 152.0 GB
File System: NTFS
      Model: Intel Optane+298GBHDD

--------------
System Devices
--------------
     Name: Mobile 7th Generation Intel(R) Processor Family I/O LPC Controller (U with iHDCP2.2 Premium) - 9D4E
Device ID: PCI\VEN_8086&DEV_9D4E&SUBSYS_20688086&REV_21\3&11583659&0&F8
   Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.19041.1202 (English), 9/15/2021 02:20:34, 20280 bytes

     Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O Thermal subsystem - 9D31
Device ID: PCI\VEN_8086&DEV_9D31&SUBSYS_20688086&REV_21\3&11583659&0&A2
   Driver: n/a

     Name: Realtek PCIE CardReader
Device ID: PCI\VEN_10EC&DEV_5229&SUBSYS_20688086&REV_01\4&3AC58DBC&0&00E7
   Driver: C:\WINDOWS\system32\DRIVERS\RtsP2Stor.sys, 10.00.18362.29098 (English), 5/15/2019 20:23:14, 356344 bytes
   Driver: C:\WINDOWS\SysWOW64\RsCRIcon.dll, 1.10.0000.0000 (English), 5/15/2019 20:23:14, 9908576 bytes

     Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O SMBUS - 9D23
Device ID: PCI\VEN_8086&DEV_9D23&SUBSYS_20688086&REV_21\3&11583659&0&FC
   Driver: n/a

     Name: Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
Device ID: PCI\VEN_8086&DEV_9D2F&SUBSYS_20688086&REV_21\3&11583659&0&A0
   Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.1566 (English), 2/16/2022 05:42:22, 624976 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.1566 (English), 2/16/2022 05:42:22, 138976 bytes

     Name: Intel(R) Iris(R) Plus Graphics 640
Device ID: PCI\VEN_8086&DEV_5926&SUBSYS_20688086&REV_06\3&11583659&0&10
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdkmd64.sys, 24.20.0100.6286 (English), 10/3/2018 20:55:00, 14072744 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iglhxs64.vp, 10/3/2018 20:37:10, 4830 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd10iumd64.dll, 24.20.0100.6286 (English), 10/3/2018 23:54:58, 21729968 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd11dxva64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:02, 57102760 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd12dxva64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:06, 58557800 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd12umd64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:08, 20367048 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdgmm64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:18, 608568 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxcmrt64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:26, 218416 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfx11cmrt64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:24, 218808 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdumdim64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:24, 2019736 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd9dxva64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:12, 57386184 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdail64.dll, 10/3/2018 20:54:56, 198744 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iga64.dll, 10/3/2018 23:54:52, 2870536 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igc64.dll, 24.20.0100.6286 (English), 10/3/2018 23:54:54, 33149488 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\UniversalAdapter64.dll, 10/3/2018 23:55:42, 179352 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\common_clang64.dll, 4.03.0000.0000 (English), 10/3/2018 23:54:52, 53922480 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdfcl64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:16, 781464 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdmd64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:22, 4005536 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdde64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:14, 456120 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdinfo64.dll, 10/3/2018 23:55:20, 153272 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdext64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:16, 160024 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd10idpp64.dll, 24.20.0100.6286 (English), 10/3/2018 23:54:56, 563488 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd10iumd32.dll, 24.20.0100.6286 (English), 10/3/2018 23:54:56, 20694960 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd11dxva32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:00, 55523616 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd12dxva32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:04, 56925064 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd12umd32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:06, 19909608 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdgmm32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:18, 566136 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdumdim32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:22, 1800120 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd9dxva32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:10, 55663784 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdail32.dll, 10/3/2018 20:54:54, 171600 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxcmrt32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:26, 185688 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfx11cmrt32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:24, 184664 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iga32.dll, 10/3/2018 23:54:52, 2427104 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igc32.dll, 24.20.0100.6286 (English), 10/3/2018 23:54:54, 29459408 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\UniversalAdapter32.dll, 10/3/2018 23:55:40, 262776 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\common_clang32.dll, 4.03.0000.0000 (English), 10/3/2018 23:54:50, 39501392 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdfcl32.dll, 24.20.0100.6286 (English), 10/3/2018 20:54:58, 818264 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdmd32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:20, 3095552 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdde32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:14, 375960 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdinfo32.dll, 10/3/2018 23:55:18, 131192 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdext32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:16, 132824 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igd10idpp32.dll, 24.20.0100.6286 (English), 10/3/2018 23:54:56, 536704 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iglhxo64.vp, 10/3/2018 20:37:10, 43885 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iglhxc64.vp, 10/3/2018 20:37:10, 43480 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iglhxg64.vp, 10/3/2018 20:37:10, 43774 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iglhxo64_dev.vp, 10/3/2018 20:37:10, 43899 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iglhxc64_dev.vp, 10/3/2018 20:37:10, 43816 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iglhxg64_dev.vp, 10/3/2018 20:37:10, 43102 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iglhxa64.vp, 10/3/2018 20:37:10, 1125 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\iglhxa64.cpa, 10/3/2018 20:37:10, 1376256 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\IntelCpHDCPSvc.exe, 25.20.0100.6286 (English), 10/3/2018 20:55:42, 505144 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\IntelCpHeciSvc.exe, 9.01.0001.1117 (English), 10/3/2018 20:55:42, 510264 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\cp_resources.bin, 10/3/2018 20:36:58, 1071820 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\difx64.exe, 1.04.0004.0000 (English), 10/3/2018 20:54:40, 175232 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxDH.dll, 6.15.0100.6286 (English), 10/3/2018 20:55:14, 1124736 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxDI.dll, 6.15.0100.6286 (English), 10/3/2018 20:55:18, 457608 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxLHM.dll, 6.15.0100.6286 (English), 10/3/2018 20:55:26, 2259216 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxEM.exe, 6.15.0100.6286 (English), 10/3/2018 20:55:20, 1024824 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxCUIServicePS.dll, 10/3/2018 20:55:12, 412032 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxCUIService.exe, 6.15.0100.6286 (English), 10/3/2018 20:55:10, 413096 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxDHLib.dll, 1.00.0000.0000 (Invariant Language), 10/3/2018 20:55:16, 123264 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxLHMLib.dll, 1.00.0000.0000 (Invariant Language), 10/3/2018 20:55:28, 23824 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\GfxUIEx.exe, 6.15.0100.6286 (English), 10/3/2018 20:54:44, 517760 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\Gfxv4_0.exe, 8.15.0100.6286 (English), 10/3/2018 20:54:46, 1242240 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\GfxResources.dll, 8.15.0100.6286 (English), 10/3/2018 20:54:44, 9335408 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\MetroIntelGenericUIFramework.dll, 1.00.0000.0000 (English), 10/3/2018 20:55:58, 646928 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxCPL.cpl, 10/3/2018 20:55:08, 286592 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxDTCM.dll, 6.15.0100.6286 (English), 10/3/2018 20:55:18, 193808 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxext.exe, 6.15.0100.6286 (English), 10/3/2018 20:55:24, 361784 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxexps.dll, 6.15.0010.3682 (English), 10/3/2018 23:55:28, 56536 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\GfxDownloadWrapper.exe, 8.15.0100.6286 (English), 10/3/2018 20:54:40, 159872 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxSDK.exe, 10/3/2018 20:55:30, 1147192 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxSDKLib.dll, 1.00.0000.0000 (Invariant Language), 10/3/2018 20:55:32, 101136 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\ColorImageEnhancement.wmv, 10/3/2018 20:36:58, 375173 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\ImageStabilization.wmv, 10/3/2018 20:37:10, 403671 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\FilmModeDetection.wmv, 10/3/2018 20:36:58, 641530 bytes
   Driver: C:\WINDOWS\system32\igfxCPL.cpl, 10/3/2018 20:55:08, 286592 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igfxexps32.dll, 6.15.0010.3682 (English), 10/3/2018 20:55:22, 54032 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\ig9icd64.dll, 24.20.0100.6286 (English), 10/3/2018 20:54:52, 15572568 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\ig9icd32.dll, 24.20.0100.6286 (English), 10/3/2018 20:54:52, 12231768 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\OSSCOPYRIGHT, 10/3/2018 20:37:14, 1372 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igvk64.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:28, 10562048 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igvk64.json, 10/3/2018 20:37:10, 137 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\VulkanRT-EULA.txt, 10/3/2018 20:37:14, 895 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\VulkanRT-Installer.exe, 1.01.0077.0000 (English), 10/3/2018 20:56:58, 1061680 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igvk32.dll, 24.20.0100.6286 (English), 10/3/2018 23:55:28, 9476832 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igvk32.json, 10/3/2018 20:37:10, 137 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\llvm_release_license.txt, 7/26/2018 06:40:20, 1981 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\readme.txt, 7/26/2018 06:40:20, 9788 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\version.ini, 7/26/2018 06:40:22, 32 bytes
   Driver: C:\WINDOWS\SysWow64\Intel_OpenCL_ICD32.dll, 2.01.0001.0000 (English), 10/3/2018 20:55:48, 121104 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\task_executor32.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:26, 398720 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\OclCpuBackend32.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:24, 12883848 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\intelocl32.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:16, 1364240 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\cpu_device32.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:10, 567056 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8.rtl, 7/26/2018 06:40:20, 2527472 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.o, 7/26/2018 06:40:20, 394116 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.rtl, 7/26/2018 06:40:20, 978088 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9.rtl, 7/26/2018 06:40:18, 2486680 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.o, 7/26/2018 06:40:18, 381364 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.rtl, 7/26/2018 06:40:18, 977952 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9.rtl, 7/26/2018 06:40:20, 1498332 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.o, 7/26/2018 06:40:20, 327948 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.rtl, 7/26/2018 06:40:20, 870628 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clang_compiler32.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:06, 2049296 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_n8.dll, 3.06.0002.0000 (English), 10/3/2018 20:56:46, 7164800 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_g9.dll, 3.06.0002.0000 (English), 10/3/2018 20:56:40, 6313344 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_s9.dll, 3.06.0002.0000 (English), 10/3/2018 20:56:48, 6120832 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\ocltbbmalloc32.dll, 2018.00.2018.0412 (English), 10/3/2018 20:56:34, 105072 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\ocltbb32.dll, 2018.00.2018.0412 (English), 10/3/2018 20:56:30, 218224 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\common\clbltfnshared.rtl, 7/26/2018 06:40:20, 1315452 bytes
   Driver: C:\WINDOWS\system32\Intel_OpenCL_ICD64.dll, 2.01.0001.0000 (English), 10/3/2018 20:55:50, 146192 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\task_executor64.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:28, 495488 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\OclCpuBackend64.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:24, 17409920 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\intelocl64.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:16, 1749776 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\cpu_device64.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:12, 750352 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8.rtl, 7/26/2018 06:40:18, 2536784 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.o, 7/26/2018 06:40:18, 421600 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.rtl, 7/26/2018 06:40:18, 1053120 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9.rtl, 7/26/2018 06:40:18, 2495784 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.o, 7/26/2018 06:40:18, 401264 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.rtl, 7/26/2018 06:40:18, 1052984 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9.rtl, 7/26/2018 06:40:18, 1507348 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.o, 7/26/2018 06:40:18, 346040 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.rtl, 7/26/2018 06:40:18, 945776 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clang_compiler64.dll, 7.06.0000.0716 (English), 10/3/2018 20:56:08, 2743056 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_h8.dll, 3.06.0002.0000 (English), 10/3/2018 20:56:44, 7455616 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_e9.dll, 3.06.0002.0000 (English), 10/3/2018 20:56:40, 6800768 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_l9.dll, 3.06.0002.0000 (English), 10/3/2018 20:56:44, 6612352 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\ocltbbmalloc64.dll, 2018.00.2018.0412 (English), 10/3/2018 20:56:38, 143472 bytes
   Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\ocltbb64.dll, 2018.00.2018.0412 (English), 10/3/2018 20:56:32, 280688 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\IntelOpenCL32.dll, 24.20.0100.6286 (English), 10/3/2018 20:55:44, 1198864 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdrcl32.dll, 10/3/2018 20:55:04, 3972480 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\IntelOpenCL64.dll, 24.20.0100.6286 (English), 10/3/2018 20:55:46, 1556752 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igdrcl64.dll, 10/3/2018 20:55:06, 4445568 bytes
   Driver: C:\WINDOWS\SysWow64\libEGL.dll, 10/3/2018 20:55:52, 149264 bytes
   Driver: C:\WINDOWS\SysWow64\libGLESv1_CM.dll, 10/3/2018 20:55:54, 133392 bytes
   Driver: C:\WINDOWS\SysWow64\libGLESv2.dll, 10/3/2018 20:55:56, 168208 bytes
   Driver: C:\Program Files\Intel\Media SDK\libmfxhw32.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:32, 18537896 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfxplugin32_hw.dll, 1.18.0008.0002 (English), 10/3/2018 20:56:00, 11592464 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_32.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:36, 2598656 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_32.dll, 8.18.0008.0002 (English), 10/3/2018 20:56:04, 2448656 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_32.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:38, 2612448 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_32.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:40, 2606624 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_32.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:34, 2442520 bytes
   Driver: C:\Program Files\Intel\Media SDK\c_32.cpa, 7/26/2018 06:40:12, 1361159 bytes
   Driver: C:\Program Files\Intel\Media SDK\cpa_32.vp, 10/3/2018 20:36:58, 1125 bytes
   Driver: C:\Program Files\Intel\Media SDK\dev_32.vp, 10/3/2018 20:36:58, 57143 bytes
   Driver: C:\Program Files\Intel\Media SDK\he_32.vp, 10/3/2018 20:36:58, 70349 bytes
   Driver: C:\Program Files\Intel\Media SDK\mj_32.vp, 10/3/2018 20:37:12, 65605 bytes
   Driver: C:\Program Files\Intel\Media SDK\h265e_32.vp, 10/3/2018 20:36:58, 72005 bytes
   Driver: C:\Program Files\Intel\Media SDK\vp9e_32.vp, 10/3/2018 20:37:14, 71596 bytes
   Driver: C:\Program Files\Intel\Media SDK\vr360sdk32.dll, 10/3/2018 20:56:54, 599432 bytes
   Driver: C:\Program Files\Intel\Media SDK\libmfxhw64.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:34, 19653480 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfxplugin64_hw.dll, 1.18.0008.0002 (English), 10/3/2018 20:56:02, 21197072 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_64.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:36, 3178784 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_64.dll, 8.18.0008.0002 (English), 10/3/2018 20:56:06, 2999568 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_64.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:38, 3200352 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9ve_64.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:40, 3192992 bytes
   Driver: C:\Program Files\Intel\Media SDK\mfx_mft_encrypt_64.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:34, 2980128 bytes
   Driver: C:\Program Files\Intel\Media SDK\c_64.cpa, 7/26/2018 06:40:12, 1376256 bytes
   Driver: C:\Program Files\Intel\Media SDK\cpa_64.vp, 10/3/2018 20:36:58, 1125 bytes
   Driver: C:\Program Files\Intel\Media SDK\dev_64.vp, 10/3/2018 20:36:58, 56359 bytes
   Driver: C:\Program Files\Intel\Media SDK\he_64.vp, 10/3/2018 20:36:58, 13401 bytes
   Driver: C:\Program Files\Intel\Media SDK\mj_64.vp, 10/3/2018 20:37:12, 13185 bytes
   Driver: C:\Program Files\Intel\Media SDK\h265e_64.vp, 10/3/2018 20:36:58, 13985 bytes
   Driver: C:\Program Files\Intel\Media SDK\vp9e_64.vp, 10/3/2018 20:37:14, 13832 bytes
   Driver: C:\Program Files\Intel\Media SDK\vr360sdk64.dll, 10/3/2018 20:56:56, 598400 bytes
   Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:30, 242328 bytes
   Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 8.18.0008.0002 (English), 10/3/2018 23:55:30, 209816 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_9af403f73c0e9f69\igxpco64.dll, 1.03.0025.0000 (English), 10/3/2018 20:55:34, 236304 bytes

     Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller
Device ID: PCI\VEN_8086&DEV_9D71&SUBSYS_20688086&REV_21\3&11583659&0&FB
   Driver: C:\WINDOWS\system32\DRIVERS\IntcAudioBus.sys, 9.21.0000.4260 (English), 9/4/2019 04:35:02, 277192 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.19041.0746 (English), 1/13/2021 05:55:06, 97792 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.19041.0746 (English), 1/13/2021 05:55:06, 388608 bytes

     Name: Intel(R) Xeon(R) E3 - 1200 v6/7th Gen Intel(R) Core(TM) Host Bridge/DRAM Registers - 5904
Device ID: PCI\VEN_8086&DEV_5904&SUBSYS_20688086&REV_03\3&11583659&0&00
   Driver: n/a

     Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O PMC - 9D21
Device ID: PCI\VEN_8086&DEV_9D21&SUBSYS_20688086&REV_21\3&11583659&0&FA
   Driver: n/a

     Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O PCI Express Root Port #8 - 9D17
Device ID: PCI\VEN_8086&DEV_9D17&SUBSYS_20688086&REV_F1\3&11583659&0&E7
   Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/14/2021 15:43:08, 469840 bytes

     Name: Intel(R) Xeon(R) E3 - 1200/1500 v5/6th Gen Intel(R) Core(TM) Gaussian Mixture Model - 1911
Device ID: PCI\VEN_8086&DEV_1911&SUBSYS_20688086&REV_00\3&11583659&0&40
   Driver: n/a

     Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O PCI Express Root Port #6 - 9D15
Device ID: PCI\VEN_8086&DEV_9D15&SUBSYS_20688086&REV_F1\3&11583659&0&E5
   Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/14/2021 15:43:08, 469840 bytes

     Name: Intel(R) Dual Band Wireless-AC 8265
Device ID: PCI\VEN_8086&DEV_24FD&SUBSYS_90108086&REV_78\4&18747CB7&0&00E5
   Driver: C:\WINDOWS\system32\DRIVERS\Netwtw06.sys, 20.70.0025.0002 (English), 7/12/2021 21:50:22, 8902224 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\Netwfw06.dat, 7/12/2021 17:07:06, 2632928 bytes
   Driver: C:\WINDOWS\system32\IntelIHVRouter06.dll, 22.12070.0000.0001 (English), 7/12/2021 21:50:20, 1518152 bytes

     Name: Intel(R) Chipset SATA/PCIe RST Premium Controller
Device ID: PCI\VEN_8086&DEV_282A&SUBSYS_20688086&REV_21\3&11583659&0&B8
   Driver: C:\WINDOWS\system32\DRIVERS\iaStorAC.sys, 18.30.0001.1138 (English), 8/15/2020 10:45:20, 1421688 bytes
   Driver: C:\WINDOWS\system32\DRIVERS\iaStorAfs.sys, 18.00.0001.1138 (English), 8/15/2020 10:45:22, 73080 bytes
   Driver: C:\WINDOWS\system32\iaStorAfsService.exe, 18.00.0001.1138 (English), 8/15/2020 10:45:22, 2965880 bytes
   Driver: C:\WINDOWS\system32\iaStorAfsNative.exe, 18.00.0001.1138 (English), 8/15/2020 10:45:22, 219512 bytes
   Driver: C:\WINDOWS\system32\OptaneEventLogMsg.dll, 18.00.0001.1138 (English), 8/15/2020 10:45:24, 23416 bytes
   Driver: C:\WINDOWS\system32\Optane.dll, 18.00.0001.1138 (English), 8/15/2020 10:45:24, 119672 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iastorac.inf_amd64_ef0d14a478b232f4\HfcDisableService.exe, 18.00.0001.1138 (English), 8/15/2020 10:45:18, 1653112 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iastorac.inf_amd64_ef0d14a478b232f4\RstMwService.exe, 18.00.0001.1138 (English), 8/15/2020 10:45:24, 1904504 bytes
   Driver: C:\WINDOWS\system32\RstMwEventLogMsg.dll, 18.00.0001.1138 (English), 8/15/2020 10:45:24, 26488 bytes

     Name: Mobile 6th/7th Generation Intel(R) Processor Family I/O PCI Express Root Port #1 - 9D10
Device ID: PCI\VEN_8086&DEV_9D10&SUBSYS_20688086&REV_F1\3&11583659&0&E0
   Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.1387 (English), 12/14/2021 15:43:08, 469840 bytes

     Name: Intel(R) Management Engine Interface 
Device ID: PCI\VEN_8086&DEV_9D3A&SUBSYS_20688086&REV_21\3&11583659&0&B0
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\heci.inf_amd64_1308ad4bd1ad0f9f\x64\TeeDriverW10x64.sys, 2031.15.0000.1743 (English), 8/10/2020 11:36:12, 304648 bytes

     Name: Intel(R) Ethernet Connection (4) I219-V
Device ID: PCI\VEN_8086&DEV_15D8&SUBSYS_20688086&REV_21\3&11583659&0&FE
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\e1d68x64.inf_amd64_546eef898d5d49f9\e1d68x64.sys, 12.18.0009.0007 (English), 5/9/2019 01:23:44, 597872 bytes
   Driver: C:\WINDOWS\System32\DriverStore\FileRepository\e1d68x64.inf_amd64_546eef898d5d49f9\e1dmsg.dll, 10.00.0768.0000 (English), 5/9/2019 01:23:44, 88552 bytes

------------------
DirectShow Filters
------------------

DirectShow Filters:
WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.19041.1288
WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.19041.1288
WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.19041.0001
MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.19041.0001
Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.19041.0450
WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.19041.0001
WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.19041.1110
Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.19041.1165
Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.19041.1165
DV Muxer,0x00400000,0,0,qdv.dll,10.00.19041.0001
Color Space Converter,0x00400001,1,1,quartz.dll,10.00.19041.0746
WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.19041.0001
AVI Splitter,0x00600000,1,1,quartz.dll,10.00.19041.0746
VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.19041.0746
SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.19041.0001
Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.19041.1566
AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.19041.0329
StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.19041.0001
MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.0746
MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.19041.0746
SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746
VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.0746
MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.19041.0329
Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.19041.0001
SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.19041.0001
Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.0001
Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.19041.0746
MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.19041.0746
DV Splitter,0x00600000,1,2,qdv.dll,10.00.19041.0001
Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.19041.0746
Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.19041.0001
ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.19041.0746
Video Renderer,0x00800001,1,0,quartz.dll,10.00.19041.0746
MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.19041.0001
Line 21 Decoder,0x00600000,1,1,,
Video Port Manager,0x00600000,2,1,quartz.dll,10.00.19041.0746
Video Renderer,0x00400000,1,0,quartz.dll,10.00.19041.0746
VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.19041.0001
WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.19041.0001
VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,
File writer,0x00200000,1,0,qcap.dll,10.00.19041.0001
DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.19041.0746
Overlay Mixer2,0x00200000,1,1,,
AVI Draw,0x00600064,9,1,quartz.dll,10.00.19041.0746
Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.0001
WST Pager,0x00200000,1,1,WSTPager.ax,10.00.19041.0001
MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.19041.0329
DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.19041.0001
SampleGrabber,0x00200000,1,1,qedit.dll,10.00.19041.0746
Null Renderer,0x00200000,1,0,qedit.dll,10.00.19041.0746
MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.19041.0001
Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.19041.0001
StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.19041.0001
Smart Tee,0x00200000,1,2,qcap.dll,10.00.19041.0001
Overlay Mixer,0x00200000,0,0,,
AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.0746
AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.19041.0746
Wave Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746
MIDI Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746
Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746
File stream renderer,0x00400000,1,1,quartz.dll,10.00.19041.0746
Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.19041.0001
StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.19041.0001
AVI Mux,0x00200000,1,0,qcap.dll,10.00.19041.0001
Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.19041.0746
File Source (Async.),0x00400000,0,1,quartz.dll,10.00.19041.0746
File Source (URL),0x00400000,0,1,quartz.dll,10.00.19041.0746
Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.19041.0001
Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.19041.0546
BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.19041.0001
MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.19041.0746

WDM Streaming Tee/Splitter Devices:
Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.0746

Video Compressors:
WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.19041.0867
WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.19041.0001
MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.19041.0001
DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.19041.0001
MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.19041.0746

Audio Compressors:
WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.19041.0508
WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.19041.0508
IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.0746
PCM,0x00200000,1,1,quartz.dll,10.00.19041.0746
Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.0746
GSM 6.10,0x00200000,1,1,quartz.dll,10.00.19041.0746
CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.19041.0746
CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.19041.0746
MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.19041.0746

Audio Capture Sources:
Microphone (Realtek(R) Audio),0x00200000,0,0,qcap.dll,10.00.19041.0001
Microphone Array (Realtek(R) Audio),0x00200000,0,0,qcap.dll,10.00.19041.0001

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

Midi Renderers:
Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.19041.0746
Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.19041.0746

WDM Streaming Capture Devices:
Realtek HD Audio Mic Array input,0x00200000,1,1,ksproxy.ax,10.00.19041.0746
,0x00000000,0,0,,
Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,10.00.19041.0746
Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.19041.0746

WDM Streaming Rendering Devices:
Intel(R) Display Audio Output 1,0x00200000,1,1,ksproxy.ax,10.00.19041.0746
Realtek HD Audio output with SST,0x00200000,2,2,ksproxy.ax,10.00.19041.0746

BDA Network Providers:
Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001
Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001
Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001
Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001
Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.19041.0001

Multi-Instance Capable VBI Codecs:
VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.0746

BDA Transport Information Renderers:
BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.19041.0001
MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.19041.0001

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

Audio Renderers:
Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746
Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.19041.0746
Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.19041.0746
DirectSound: PB328 (Intel(R) Display Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746
DirectSound: Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746
PB328 (Intel(R) Display Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746


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

[HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred]

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

MEDIASUBTYPE_DVD_LPCM_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS
MEDIASUBTYPE_MPEG2_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS
MEDIASUBTYPE_MPEG2_VIDEO, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS
{78766964-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
{7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
MEDIASUBTYPE_mp4s, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
{64697678-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
{58564944-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
{5634504D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
MEDIASUBTYPE_MP4S, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
MEDIASUBTYPE_WMVR, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_WMVP, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject
{44495658-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
MEDIASUBTYPE_WMVA, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_mpg4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject
MEDIASUBTYPE_MPG4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject
MEDIASUBTYPE_h264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS
MEDIASUBTYPE_H264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS
MEDIASUBTYPE_WMV3, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_mp43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject
MEDIASUBTYPE_MP43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject
MEDIASUBTYPE_m4s2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
MEDIASUBTYPE_WMV2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_MSS2, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject
MEDIASUBTYPE_M4S2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject
MEDIASUBTYPE_WVP2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_mp42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject
MEDIASUBTYPE_MP42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject
MEDIASUBTYPE_WMV1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_MSS1, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject
MEDIASUBTYPE_WVC1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_AVC1, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS
MEDIASUBTYPE_MPEG_LOAS, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS
MEDIASUBTYPE_MPEG_ADTS_AAC, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS
MEDIASUBTYPE_WMAUDIO_LOSSLESS, WMAudio Decoder DMO, CLSID_CWMADecMediaObject
MEDIASUBTYPE_WMAUDIO3, WMAudio Decoder DMO, CLSID_CWMADecMediaObject
WMMEDIASUBTYPE_WMAudioV8, WMAudio Decoder DMO, CLSID_CWMADecMediaObject
MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder DMO, CLSID_CWMADecMediaObject
MEDIASUBTYPE_RAW_AAC1, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS
WMMEDIASUBTYPE_MP3, MP3 Decoder DMO, CLSID_CMP3DecMediaObject
MEDIASUBTYPE_MPEG1Payload, MPEG Video Decoder, CLSID_CMpegVideoCodec
MEDIASUBTYPE_MPEG1Packet, MPEG Video Decoder, CLSID_CMpegVideoCodec
{6C737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec
{64737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec
{64687664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec
MEDIASUBTYPE_MJPG, MJPEG Decompressor, CLSID_MjpegDec
{20637664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec
MEDIASUBTYPE_MPEG1AudioPayload, MPEG Audio Decoder, CLSID_CMpegAudioCodec
WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject
WMMEDIASUBTYPE_WMSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject


---------------------------
Media Foundation File Versions
---------------------------

  mfcore.dll, 10.00.19041.1566
  mfreadwrite.dll, 10.00.19041.0746
  mfcaptureengine.dll, 10.00.19041.0906
  mfsensorgroup.dll, 10.00.19041.1503
  windows.media.dll, 10.00.19041.1566
  frameserver.dll, 10.00.19041.1503
  frameserverclient.dll, 10.00.19041.1503


---------------------------
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, 8.18.0008.0002
  Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.19041.1566
  DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.19041.0001
  Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.19041.0450
  Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.19041.1566
  WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.19041.0001
  WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.19041.1110
  MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.19041.1348
  Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.19041.1165
  Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.19041.1165
  VP9VideoExtensionDecoder
  WebpImageExtension
  HEIFImageExtension
Video Encoders:
  Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 8.18.0008.0002
  Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 8.18.0008.0002
  H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.19041.1566
  WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.19041.0867
  H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.19041.0001
  WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.19041.0001
  Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.19041.0001
  VP9VideoExtensionEncoder
  HEIFImageExtension
Video Effects:
  Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.19041.0746
  Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.19041.0867
  VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.19041.0746
  Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.19041.0746
  Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.19041.1110
Video Processor:
  Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.19041.1566
Audio Decoders:
  Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.19041.1566
  MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.19041.0001
  WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.19041.1288
  Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.19041.1165
  A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.19041.1566
  GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.19041.1566
  WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.19041.1288
  Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.19041.0746
  Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.19041.1566
  Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.19041.1165
  WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.19041.0001
  G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.19041.1566
  IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.19041.1566
  MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.19041.0001
  Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.19041.0746
  ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.19041.1566
  Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.19041.0746
  DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.19041.0746
Audio Encoders:
  LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.19041.0746
  MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.19041.1566
  Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.19041.0746
  WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.19041.0508
  MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.19041.0001
  Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.19041.0001
  WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.19041.0508
  Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.19041.0001
  Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.19041.0746
  Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.19041.0001
Audio Effects:
  AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.19041.0001
  Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.19041.0001
Multiplexers:
  Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.19041.1566
Others:
  Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.19041.1566


--------------------------------------------
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, {A8721937-E2FB-4D7A-A9EE-4EB08C890B6E}, MF SBE Source ByteStreamHandler
.dvr-ms, {65964407-A5D8-4060-85B0-1CCD63F768E2}, dvr-ms Byte Stream Handler, Preferred
.ec3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred
.flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred
.m2t, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.m2ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
.m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
.mk3d, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred
.mka, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred
.mks, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred
.mkv, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred
.mod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.mov, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
.mp2v, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred
.mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
.mp4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
.mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred
.mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.mpg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.mts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.nsc, {B084785C-DDE0-4D30-8CA8-05A373E185BE}, NSC Byte Stream Handler, Preferred
.sami, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred
.smi, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred
.tod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.uvu, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
.vob, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
.wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred
.weba, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred
.webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred
.wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred
.wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred
.wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred
.wtv, {65964407-A5D8-4060-85B0-1CCD63F768E2}, WTV Byte Stream Handler, Preferred
audio/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
audio/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
audio/aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred
audio/aacp, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred
audio/eac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred
audio/flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred
audio/L16, {3FFB3B8C-EB99-472B-8902-E1C1B05F07CF}, LPCM Byte Stream Handler, Preferred
audio/mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred
audio/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
audio/MP4A-LATM, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
audio/mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred
audio/mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred
audio/mpeg3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred
audio/vnd.dlna.adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred
audio/vnd.dolby.dd-raw, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred
audio/wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred
audio/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred
audio/x-aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred
audio/x-flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred
audio/x-m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
audio/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred
audio/x-mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred
audio/x-mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred
audio/x-ms-wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred
audio/x-wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred
video/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
video/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
video/avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred
video/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
video/mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
video/msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred
video/vnd.dece.mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
video/vnd.dlna.mpeg-tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred
video/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred
video/x-m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred
video/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred
video/x-ms-asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred
video/x-ms-wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred
video/x-ms-wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred
video/x-msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred


--------------------------------
Media Foundation Scheme Handlers
--------------------------------

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers]
[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred]

<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
rtsps:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred
rtspt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred
rtspu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred
sdp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred


-------------------------------------
Preferred Media Foundation Transforms
-------------------------------------

[HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\Preferred]

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

{EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}
{E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}
MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}
MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}
{A61AC364-AD0E-4744-89FF-213CE0DF8804}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}
{A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}
{7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
{73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}
MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}
MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}
MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}
{63616C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}
MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
{53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}
MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
{3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT
MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject
MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject
MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT
MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
{33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject
MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject
MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject
MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT
MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject
MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject
MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject
MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}
MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject
MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}
{0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}
{00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}
{0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}
{00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}
{00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}
{00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}
MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT
MFAudioFormat_ADTS, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT
MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject
MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject
MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject
MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject
MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT
MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject
MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}
{00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}
{00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}
KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}
{00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}
KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}
WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject
MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject


-------------------------------------
Disabled Media Foundation Transforms
-------------------------------------

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

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

Problem signature:
P1: 10.0.19041.1525:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x2bc3acfa
P7: 
P8: 
P9: 
P10: 


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

Problem signature:
P1: 10.0.19041.1525:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x2bc3acfa
P7: 
P8: 
P9: 
P10: 


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

Problem signature:
P1: 10.0.19041.1525:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x2bc3acfa
P7: 
P8: 
P9: 
P10: 


+++ WER3 +++:
Fault bucket 1253240109239416703, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: explorer.exe
P2: 10.0.19041.1503
P3: 261d1767
P4: StackHash_b4ee
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: PCH_3B_FROM_unknown+0x00000000
P9: 
P10: 


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

Problem signature:
P1: explorer.exe
P2: 10.0.19041.1503
P3: 261d1767
P4: StackHash_b4ee
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: PCH_3B_FROM_unknown+0x00000000
P9: 
P10: 


+++ WER5 +++:
Fault bucket 2119733130701250076, type 5
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.19041.1525:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x2bc3acfa
P7: 
P8: 
P9: 
P10: 


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

Problem signature:
P1: 10.0.19041.1525:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x2bc3acfa
P7: 
P8: 
P9: 
P10: 


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

Problem signature:
P1: 10.0.19041.1525:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x2bc3acfa
P7: 
P8: 
P9: 
P10: 


+++ WER8 +++:
Fault bucket 1197582946575137397, type 5
Event Name: WindowsWcpOtherFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.19041.1490:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x2bc3acfa
P7: 
P8: 
P9: 
P10: 


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

Problem signature:
P1: 10.0.19041.1490:1
P2: wcp\componentstore\storelayout.cpp
P3: ComponentStore::CRawStoreLayout::HydrateFileUsingForwardAndReverseDeltas
P4: 1682
P5: 800f0984
P6: 0x2bc3acfa
P7: 
P8: 
P9: 
P10: 


...#SSU#...