- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I use to work with a latop Dell G3 windows 11 and it supports my LG ultra - wide screen model 25UM58-P with a resolution of 2560 x 1080.
But now I have a new HP 17" HP Laptop 17T-CN300 with Intel Xe Graphics card, even after installing the graphics drivers from HP, the laptop offers as maximum resolution 1920 x 1080 for this LG monitor.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, cvmontuy.
Thank you for posting in our Community.
I understand that you have a laptop. Since this is an OEM (HP laptop) original equipment manufacturer device, please take into consideration that our support may be limited since we are not familiar with the technology, settings, customizations, custom drivers, and features that the OEM has designed and installed your system, nevertheless, I will do my best to assist you with your concern.
It's strange that despite installing the graphics drivers from HP, the laptop is restricting the maximum resolution for the LG monitor to 1920 x 1080. This is particularly odd considering that your previous Dell G3 with Windows 11 supported a higher resolution of 2560 x 1080. This discrepancy could be due to various reasons such as compatibility issues between the graphics card and the monitor, driver configurations, or settings within the operating system. I'd like to delve deeper and verify specifics like the graphics models, precise driver versions, and any system errors. Utilizing the Intel SSU tool will enable us to collect detailed information about your system setup, which could aid in identifying the underlying cause of this issue.
Looking forward to your response. Have a nice day!
Best regards,
Von M.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you very much for your assistance. I understand that this should be more on HP's side. I have created a ticket there, but I still haven't received an answer. The person from HP who initially assisted me reviewed my case and said that it's "probably a hardware limitation". In the previous message, you will find an attachment containing the SSU tool report, which I have also copied below. Thanks again.
=========================================================================
# SSU Scan Information
Scan Info:
Version:"3.0.0.2"
Date:"05-09-2024"
Time:"00:00:51.6855789"
# Scanned Hardware
Computer:
BaseBoard Manufacturer:"HP"
BIOS Mode:"Legacy"
BIOS Version/Date:"Insyde F.06 , 02-01-2024 12:00 AM"
CD or DVD:"Not Available"
Embedded Controller Version:"65.14"
Platform Role:"Mobile"
Processor:"13th Gen Intel(R) Core(TM) i7-1355U , GenuineIntel"
Secure Boot State:"Off"
SMBIOS Version:"3.4"
Sound Card:"USB Audio Device"
Sound Card:"Intel® Smart Sound Technology for Digital Microphones"
Sound Card:"Intel® Smart Sound Technology for Bluetooth® Audio"
Sound Card:"Realtek High Definition Audio"
System Manufacturer:"HP"
System Model:"HP Laptop 17t-cn300"
System SKU:"767L0AV"
System Type:"x64-based PC"
- "Display"
Intel ® Graphics Driver Version:"Not Available"
- "Intel(R) Iris(R) Xe Graphics"
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) Xe Graphics"
Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Iris+Xe+Graphics"
CoInstallers:"oem16.inf,iRPLPD_w10_DS,Internal,Intel(R) Iris(R) Xe Graphics Family"
Color Table Entries:"4294967296"
Dedicated Video Memory:"Not Available"
Driver:"igdkmdn64.sys"
Driver Date:"06-14-2023 06:00 PM"
Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_0db786bd9a6ade98\igdkmdn64.sys"
Driver Provider:"Intel Corporation"
Driver Version:"31.0.101.4502"
INF:"oem16.inf"
INF Section:"iRPLPD_w10_DS"
Install Date:"Not Available"
Installed Drivers:"<>,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0db786bd9a6ade98\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0db786bd9a6ade98\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_0db786bd9a6ade98\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_A7A1&SUBSYS_8BBA103C&REV_04\3&11583659&0&10"
Power Management Capabilities:"Not Available"
Power Management Supported:"Not Available"
Refresh Rate - Current:"40 Hz"
Refresh Rate - Maximum:"60 Hz"
Refresh Rate - Minimum:"40 Hz"
Resolution:"1600 X 900"
Scan Mode:"Noninterlaced"
Service Name:"igfxn"
Status:"OK"
Video Architecture:"VGA"
Video Memory:"Unknown"
Video Processor:"Intel(R) Iris(R) Xe Graphics Family"
- "Memory"
Physical Memory (Available):"32.02 GB"
Physical Memory (Installed):"64 GB"
Physical Memory (Total):"63.72 GB"
- "BANK 0"
Capacity:"32 GB"
Channel:"Bottom-slot 1(left)"
Configured Clock Speed:"3200 MHz"
Configured Voltage:"1200 millivolts"
Data Width:"64 bits"
Form Factor:"SODIMM"
Interleave Position:"First position"
Manufacturer:"0x0C26"
Maximum Voltage:"Not Available"
Memory Type:"Unknown"
Minimum Voltage:"Not Available"
Part Number:"TIMETEC-S32G-3200"
Serial Number:"03CDFEF3"
Status:"Not Available"
Type:"Synchronous"
- "BANK 0"
Capacity:"32 GB"
Channel:"Bottom-slot 2(right)"
Configured Clock Speed:"3200 MHz"
Configured Voltage:"1200 millivolts"
Data Width:"64 bits"
Form Factor:"SODIMM"
Interleave Position:"First position"
Manufacturer:"0x0C26"
Maximum Voltage:"Not Available"
Memory Type:"Unknown"
Minimum Voltage:"Not Available"
Part Number:"TIMETEC-S32G-3200"
Serial Number:"03CDFF1B"
Status:"Not Available"
Type:"Synchronous"
- "Motherboard"
Availability:"Running or Full Power"
BIOS:"F.06, HPQOEM - 2"
Caption:"Motherboard"
Chipset:"Not Available"
Date:"01-31-2024 06:00 PM"
Install Date:"Not Available"
Last Error Code:"Not Available"
Last Error Code Description:"Not Available"
Manufacturer:"HP"
Model:"Not Available"
Part Number:"Not Available"
PNP Device ID:"Not Available"
Power Management Capabilities:"Not Available"
Power Management Supported:"Not Available"
Product:"8BBA"
Serial Number:"PRTFE00WBJA03Q"
Status:"OK"
Version:"65.14"
- "Networking"
Intel ® Network Connections Install Options:"Not Available"
Intel ® Network Connections Version:"Not Available"
Intel ® PROSet/Wireless Software Version:"Not Available"
- "ASIX USB to Gigabit Ethernet Family Adapter"
Availability:"Running or Full Power"
Caption:"ASIX USB to Gigabit Ethernet Family Adapter"
CoInstallers:"Not Available"
Default IP Gateway:"Not Available"
DHCP Enabled:"Yes"
DHCP Lease Expires:"Not Available"
DHCP Lease Obtained:"Not Available"
DHCP Server:"Not Available"
Driver:"AxUsbEth.sys"
Driver Date:"12-15-2023 12:00 AM"
Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\axusbeth.inf_amd64_88fb34fbbab9fd2d\AxUsbEth.sys"
Driver Provider:"ASIX"
Driver Version:"3.20.1.0"
Index:"0013"
INF:"oem293.inf"
INF Section:"AX88179A.Ndi"
Install Date:"Not Available"
Installed:"Yes"
IP Address:"Not Available"
IP Subnet:"Not Available"
Last Error Code:"Not Available"
Last Error Code Description:"Not Available"
Last Reset:"05-01-2024 11:31 PM"
Location:"Port_#0002.Hub_#0003"
MAC Address:"20:7B:D2:C7:5C:9E"
Manufacturer:"ASIX"
Net Connection ID:"Ethernet"
NetCfgInstanceId:"{F25F5B52-6F83-4D17-9D49-1496AABEE397}"
PNP Device ID:"USB\VID_0B95&PID_1790\00C75C9E"
Port:"Not Available"
Power Management (Low Power):"Not Available"
Power Management (Wake On LAN):"Not Available"
Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No"
Power Management Capabilities:"Not Available"
Power Management Supported:"No"
Product Type:"ASIX USB to Gigabit Ethernet Family Adapter"
Service Name:"AX88179A"
Status:"Enabled"
Type:"Ethernet 802.3"
- "Service Bindings"
Client for Microsoft Networks:
File and Printer Sharing for Microsoft Networks:
FortiClient NDIS 6.3 Packet Filter Driver:
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:
QoS Packet Scheduler:
VirtualBox NDIS6 Bridged Networking Driver:
- "Settings"
*EEE:Energy-Efficient Ethernet:"Enabled (1)"
*FlowControl:Flow Control:"Rx & Tx Enabled (3)"
*IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)"
*LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)"
*LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)"
*ModernStandbyWoLMagicPacket:Modern standby wake on Magic packet:"Enabled (1)"
*PMARPOffload:ARP Offload:"Enabled (1)"
*PMNSOffload:NS Offload:"Enabled (1)"
*PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enable (3)"
*SelectiveSuspend:SelectiveSuspend:"Enabled (1)"
*SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)"
*SSIdleTimeout:SSIdleTimeout:"60 (60)"
*TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)"
*TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)"
*UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)"
*UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)"
*WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)"
*WakeOnPattern:Wake on pattern match:"Enabled (1)"
FlowControlMode:Flow Control Mode Select:"Passive Mode (41)"
ForceSuspend:ForceSuspend:"Disabled (0)"
FWVersion:FWVersion:"1.0.5_R3 (1.0.5_R3)"
GreenEthernet:Green Ethernet:"Disabled (0)"
IMR:Interrupt Moderation Rate:"Middle (2)"
JumboPacket:JumboPacket:"Disabled (0)"
MaskTimer:Mask WakeUp Event Timer:"8 seconds (2)"
SuspendAutoDetach:Suspend AutoDetach:"Enabled (1)"
SuspendLowPower:Suspend Low Power:"Enabled (1)"
UsbPowerSave:U1/U2 Power Saving:"0x00 (0)"
WakeOnLinkChange:Wake on link change:"Disabled (0)"
- "Bluetooth Device (Personal Area Network)"
Availability:"Running or Full Power"
Caption:"Bluetooth Device (Personal Area Network)"
CoInstallers:"Not Available"
Default IP Gateway:"Not Available"
DHCP Enabled:"Yes"
DHCP Lease Expires:"Not Available"
DHCP Lease Obtained:"Not Available"
DHCP Server:"Not Available"
Driver:"bthpan.sys"
Driver Date:"06-21-2006 12:00 AM"
Driver Path:"C:\WINDOWS\system32\drivers\bthpan.sys"
Driver Provider:"Microsoft"
Driver Version:"10.0.22621.2506"
Index:"0001"
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:"05-01-2024 11:31 PM"
Location:"Not Available"
MAC Address:"1C:CE:51:60:96:DB"
Manufacturer:"Microsoft"
Net Connection ID:"Bluetooth Network Connection"
NetCfgInstanceId:"{26706810-3287-446A-82AC-3560D04F147C}"
PNP Device ID:"BTH\MS_BTHPAN\6&18FE9849&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"
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:
- "Fortinet SSL VPN Virtual Ethernet Adapter"
Availability:"Running or Full Power"
Caption:"Fortinet SSL VPN Virtual Ethernet Adapter"
CoInstallers:"Not Available"
Default IP Gateway:"Not Available"
DHCP Enabled:"Yes"
DHCP Lease Expires:"Not Available"
DHCP Lease Obtained:"Not Available"
DHCP Server:"Not Available"
Driver:"ftsvnic.sys"
Driver Date:"08-23-2023 12:00 AM"
Driver Path:"C:\WINDOWS\system32\drivers\ftsvnic.sys"
Driver Provider:"Fortinet Inc"
Driver Version:"14.10.32.849"
Index:"0016"
INF:"oem302.inf"
INF Section:"ftsvnic.ndi"
Install Date:"Not Available"
Installed:"Yes"
IP Address:"Not Available"
IP Subnet:"Not Available"
Last Error Code:"Not Available"
Last Error Code Description:"Not Available"
Last Reset:"05-01-2024 11:31 PM"
Location:"Not Available"
MAC Address:"Not Available"
Manufacturer:"Fortinet Inc"
Net Connection ID:"Ethernet 4"
NetCfgInstanceId:"{366819E7-6F95-4019-A075-CD88C8C7A1E9}"
PNP Device ID:"ROOT\NET\0002"
Port:"Not Available"
Power Management (Low Power):"Not Available"
Power Management (Wake On LAN):"Not Available"
Power Management (Wake on Magic Packet):"Not Available"
Power Management Capabilities:"Not Available"
Power Management Supported:"No"
Product Type:"Fortinet SSL VPN Virtual Ethernet Adapter"
Service Name:"ftsvnic"
Status:"Device is disabled."
Type:"Not Available"
- "Service Bindings"
Client for Microsoft Networks:
File and Printer Sharing for Microsoft Networks:
FortiClient NDIS 6.3 Packet Filter Driver:
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:
QoS Packet Scheduler:
VirtualBox NDIS6 Bridged Networking Driver:
- "Fortinet Virtual Ethernet Adapter (NDIS 6.30)"
Availability:"Running or Full Power"
Caption:"Fortinet Virtual Ethernet Adapter (NDIS 6.30)"
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:"ftvnic.sys"
Driver Date:"04-09-2020 12:00 AM"
Driver Path:"C:\WINDOWS\system32\drivers\ftvnic.sys"
Driver Provider:"Fortinet"
Driver Version:"2020.4.9.0"
Index:"0015"
INF:"oem301.inf"
INF Section:"FTNT.ndi"
Install Date:"Not Available"
Installed:"Yes"
IP Address:"Not Available"
IP Subnet:"Not Available"
Last Error Code:"Not Available"
Last Error Code Description:"Not Available"
Last Reset:"05-01-2024 11:31 PM"
Location:"Not Available"
MAC Address:"00:09:0F:FE:00:01"
Manufacturer:"Fortinet"
Net Connection ID:"Ethernet 3"
NetCfgInstanceId:"{F06A3AAC-625F-43F3-9BB9-79E33B344BE0}"
PNP Device ID:"ROOT\NET\0001"
Port:"Not Available"
Power Management (Low Power):"Not Available"
Power Management (Wake On LAN):"Not Available"
Power Management (Wake on Magic Packet):"Not Available"
Power Management Capabilities:"Not Available"
Power Management Supported:"No"
Product Type:"Fortinet Virtual Ethernet Adapter (NDIS 6.30)"
Service Name:"ft_vnic"
Status:"Enabled"
Type:"Ethernet 802.3"
- "Service Bindings"
Client for Microsoft Networks:
File and Printer Sharing for Microsoft Networks:
FortiClient NDIS 6.3 Packet Filter Driver:
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:
QoS Packet Scheduler:
VirtualBox NDIS6 Bridged Networking Driver:
- "Realtek RTL8852BE WiFi 6 802.11ax PCIe Adapter"
Access Point:"a4:6d:a4:3b:e2:1c"
Authentication:"WPA2-Personal"
Availability:"Running or Full Power"
Caption:"Realtek RTL8852BE WiFi 6 802.11ax PCIe Adapter"
Channel:"149"
Cipher:"CCMP"
CoInstallers:"Not Available"
Connection Mode:"Profile"
Default IP Gateway:"192.168.100.1;fe80::1"
DHCP Enabled:"Yes"
DHCP Lease Expires:"05-12-2024 10:14 AM"
DHCP Lease Obtained:"05-09-2024 10:14 AM"
DHCP Server:"192.168.100.1"
Driver:"rtwlane601.sys"
Driver Date:"08-08-2023 12:00 AM"
Driver Path:"C:\WINDOWS\system32\drivers\rtwlane601.sys"
Driver Provider:"Realtek Semiconductor Corp."
Driver Version:"6001.15.145.0"
Index:"0002"
INF:"oem263.inf"
INF Section:"HP8852be.ndi.NT"
Install Date:"Not Available"
Installed:"Yes"
IP Address:"192.168.100.47;fe80::aa02:be39:8d6e:654f;2806:2f0:a5c0:ef60:fc3c:b4c:fbfa:4244;2806:2f0:a5c0:ef60:9a37:ad59:1715:6388"
IP Subnet:"255.255.255.0;64;128;64"
Last Error Code:"Not Available"
Last Error Code Description:"Not Available"
Last Reset:"05-01-2024 11:31 PM"
Location:"PCI bus 2, device 0, function 0"
MAC Address:"1C:CE:51:60:96:DA"
Manufacturer:"Realtek Semiconductor Corp."
Net Connection ID:"Wi-Fi"
NetCfgInstanceId:"{DF90D850-70DE-4498-B123-7437D7B17468}"
Network Name:"RELUM5G"
Network Type:"Infrastructure"
PNP Device ID:"PCI\VEN_10EC&DEV_B852&SUBSYS_88E3103C&REV_00\00E04CFFFE88520100"
Port:"Not Available"
Power Management (Low Power):"Not Available"
Power Management (Wake On LAN):"Not Available"
Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No"
Power Management Capabilities:"Not Available"
Power Management Supported:"No"
Product Type:"Realtek RTL8852BE WiFi 6 802.11ax PCIe Adapter"
Profile:"RELUM5G"
Radio Type:"802.11ac"
Receive Rate:"866.7 Mbps"
Service Name:"rtwlane601"
Signal Strength:"86%"
State:"connected"
Status:"Enabled"
Transmit Rate:"866.7 Mbps"
Type:"Ethernet 802.3"
- "Service Bindings"
Client for Microsoft Networks:
File and Printer Sharing for Microsoft Networks:
FortiClient NDIS 6.3 Packet Filter Driver:
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:
QoS Packet Scheduler:
VirtualBox NDIS6 Bridged Networking Driver:
- "Settings"
*WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)"
*WakeOnPattern:Wake on Pattern Match:"Enabled (1)"
AH_BcnIntv:Beacon Interval:"100 (100)"
Dot11dEnable:802.11d:"Enabled (1)"
MCCSup:Multi-Channel Concurrent:"Enabled (1)"
PreambleMode:Preamble Mode:"Short & long (2)"
PreferBand:Preferred Band:"3. 5G first (2)"
RegROAMSensitiveLevel:Roaming Aggressiveness:"4. Medium (70)"
SupportMACRandom:MAC Randomization:"Enabled (1)"
WifiProtocol_2g:2.4G Wireless Mode:"IEEE 802.11b/g/n/ax (45)"
WifiProtocol_5g:5G Wireless Mode:"IEEE 802.11a/n/ac/ax (58)"
- "VirtualBox Host-Only Ethernet Adapter"
Availability:"Running or Full Power"
Caption:"VirtualBox Host-Only Ethernet Adapter"
CoInstallers:"Not Available"
Default IP Gateway:"Not Available"
DHCP Enabled:"No"
DHCP Lease Expires:"Not Available"
DHCP Lease Obtained:"Not Available"
DHCP Server:"Not Available"
Driver:"VBoxNetAdp6.sys"
Driver Date:"04-12-2024 12:00 AM"
Driver Path:"C:\WINDOWS\system32\DRIVERS\VBoxNetAdp6.sys"
Driver Provider:"Oracle Corporation"
Driver Version:"7.0.16.12802"
Index:"0014"
INF:"oem298.inf"
INF Section:"VBoxNetAdp6.ndi"
Install Date:"Not Available"
Installed:"Yes"
IP Address:"192.168.56.1;fe80::2df8:1563:4f91:9b2a"
IP Subnet:"255.255.255.0;64"
Last Error Code:"Not Available"
Last Error Code Description:"Not Available"
Last Reset:"05-01-2024 11:31 PM"
Location:"Not Available"
MAC Address:"0A:00:27:00:00:12"
Manufacturer:"Oracle Corporation"
Net Connection ID:"Ethernet 2"
NetCfgInstanceId:"{B7B1D0C1-65B4-4CA6-A35A-100067E99CD7}"
PNP Device ID:"ROOT\NET\0000"
Port:"Not Available"
Power Management (Low Power):"Not Available"
Power Management (Wake On LAN):"Not Available"
Power Management (Wake on Magic Packet):"Not Available"
Power Management Capabilities:"Not Available"
Power Management Supported:"No"
Product Type:"VirtualBox Host-Only Ethernet Adapter"
Service Name:"VBoxNetAdp"
Status:"Enabled"
Type:"Ethernet 802.3"
- "Service Bindings"
Client for Microsoft Networks:
File and Printer Sharing for Microsoft Networks:
FortiClient NDIS 6.3 Packet Filter Driver:
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:
QoS Packet Scheduler:
VirtualBox NDIS6 Bridged Networking Driver:
- "Operating System"
.Net Framework Version:"4.0,4.8"
Boot Device:"\Device\HarddiskVolume1"
Internet Browser:"Mozilla Firefox, Google Chrome,124.0, Internet Explorer,11.1, Microsoft Edge,124.0"
Locale:"United States"
OS Manufacturer:"Microsoft Corporation"
OS Name:"Microsoft Windows 11 Pro"
Other OS Description:"Not Available"
Page File:"C:\pagefile.sys"
Page File Space:"9.50 GB"
Physical Memory (Available):"32.03 GB"
Physical Memory (Installed):"64 GB"
Physical Memory (Total):"63.72 GB"
System Directory:"C:\WINDOWS\system32"
Version:"10.0.22631 Build 22631"
Virtual Memory (Available):"30.83 GB"
Virtual Memory (Total):"73.22 GB"
Windows Directory:"C:\WINDOWS"
- "Installed Updates"
KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]"
KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]"
KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]"
KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]"
KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]"
KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]"
KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]"
KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]"
KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]"
KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]"
KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]"
KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]"
KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]"
KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]"
KB5027397:"Update [4/17/2024]"
KB5031274:"Update [4/12/2024]"
KB5036212:"Update [4/12/2024]"
KB5036620:"Update [4/17/2024]"
KB5036980:"Update [4/25/2024]"
KB5037663:"Update [4/24/2024]"
- "Processor"
- "13th Gen Intel(R) Core(TM) i7-1355U"
Architecture:"x64"
ATPO:"Not Available"
Availability:"Running or Full Power"
Caption:"Intel64 Family 6 Model 186 Stepping 3"
- "Chipset Name":"13th Gen Intel(R) Core(TM) i7-1355U"
Link:"http://www.intel.com/content/www/us/en/search.html?keyword=13th+Gen++Core+i7+1355U"
CPU Speed:"1.70 GHz"
Current Voltage:"9. 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.22621.3527"
Ext. Family:"Not Available"
Family:"Intel Core™ i7-2760QM"
FPO:"Not Available"
INF:"cpu.inf"
INF Section:"IntelPPM_Inst.NT"
Install Date:"Not Available"
Last Error Code:"Not Available"
Level 1 Cache:"10 x 96 KB"
Level 2 Cache:"10 x 6656 KB"
Level 3 Cache:"12 MB"
Load:"37%"
Manufacturer:"GenuineIntel"
Model:"186"
Name:"13th Gen Intel(R) Core(TM) i7-1355U"
Number of Cores:"10"
Number of Cores Enabled:"10"
Number of Logical Processors:"12"
Part Number:"To Be Filled By O.E.M."
Power Management Capabilities:"Not Available"
Power Management Supported:"No"
Processor ID:"BFEBFBFF000B06A3"
Revision:"Not Available"
Serial Number:"To Be Filled By O.E.M."
Service Name:"intelppm"
Status:"OK"
Stepping:"3"
Version:"Not Available"
- "Storage"
- "Generic STORAGE DEVICE USB Device"
Capablities:"Random Access, Supports Writing, Supports Removable Media"
Caption:"Generic STORAGE DEVICE USB Device"
Cylinder - Total:"7791"
Description:"Disk drive"
Driver:"Not Available"
Driver Date:"06-21-2006 12:00 AM"
Driver Version:"10.0.22621.3235"
Error Code:"Device is working properly"
Firmware Revision:"0233"
Heads - Total:"255"
Index:"1"
INF:"disk.inf"
Install Date:"Not Available"
Interface Type:"USB"
Manufacturer:"(Standard disk drives)"
Model:"Generic STORAGE DEVICE USB Device"
Name:"\\.\PHYSICALDRIVE1"
Partitions:"1"
PNP Device ID:"USBSTOR\DISK&VEN_GENERIC&PROD_STORAGE_DEVICE&REV_0233\8&15288262&0"
Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available"
Sectors - Per Track:"63"
Sectors - Total:"125162415"
Serial Number:"Not Available"
Size:"59.68 GB"
Size – Available:"47.06 GB"
Status:"OK"
Tracks - Per Cylinder:"255"
Tracks - Total:"1986705"
- "D:"
Availability:"Not Available"
Caption:"D:"
Compression Method:"Not Compressed"
Description:"Removable Disk"
File System:"exFAT"
Name:"NIKON D7200"
Serial Number:"4F70350B"
Size:"59.66 GB"
Size – Available:"47.06 GB"
Status:"Not Available"
Volume Dirty:"No"
- "NX-2TB 2280"
Capablities:"Random Access, Supports Writing"
Caption:"NX-2TB 2280"
Cylinder - Total:"249038"
Description:"Disk drive"
Driver:"Not Available"
Driver Date:"06-21-2006 12:00 AM"
Driver Version:"10.0.22621.3235"
Error Code:"Device is working properly"
Firmware Revision:"SN12962"
Heads - Total:"255"
Index:"0"
INF:"disk.inf"
Install Date:"Not Available"
Interface Type:"SCSI"
Manufacturer:"(Standard disk drives)"
Model:"NX-2TB 2280"
Name:"\\.\PHYSICALDRIVE0"
Partitions:"4"
Physical Sector Size:"4096"
PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_NX-2TB_2280\5&114A1043&0&000000"
Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available"
SCSI Bus:"0"
SCSI LUN:"0"
SCSI Port:"1"
Sectors - Per Track:"63"
Sectors - Total:"4000795470"
Serial Number:"0000_0000_0000_0000_0000_0088_9800_3990."
Size:"1.86 TB"
Size – Available:"1.51 TB"
Status:"OK"
Tracks - Per Cylinder:"255"
Tracks - Total:"63504690"
- "C:"
Availability:"Not Available"
Caption:"C:"
Compression Method:"Not Compressed"
Description:"Local Fixed Disk"
File System:"NTFS"
Name:"Not Available"
Serial Number:"E8AC1FC1"
Size:"636.63 GB"
Size – Available:"509.74 GB"
Status:"Not Available"
Volume Dirty:"No"
- "E:"
Availability:"Not Available"
Caption:"E:"
Compression Method:"Not Compressed"
Description:"Local Fixed Disk"
File System:"NTFS"
Name:"DATA"
Serial Number:"9CD3ACED"
Size:"1269.53 GB"
Size – Available:"1032.81 GB"
Status:"Not Available"
Volume Dirty:"No"
- "Seagate Expansion SCSI Disk Device"
Capablities:"Random Access, Supports Writing"
Caption:"Seagate Expansion SCSI Disk Device"
Cylinder - Total:"243201"
Description:"Disk drive"
Driver:"Not Available"
Driver Date:"06-21-2006 12:00 AM"
Driver Version:"10.0.22621.3235"
Error Code:"Device is working properly"
Firmware Revision:"0707"
Heads - Total:"255"
Index:"2"
INF:"disk.inf"
Install Date:"Not Available"
Interface Type:"SCSI"
Manufacturer:"(Standard disk drives)"
Model:"Seagate Expansion SCSI Disk Device"
Name:"\\.\PHYSICALDRIVE2"
Partitions:"2"
Physical Sector Size:"4096"
PNP Device ID:"SCSI\DISK&VEN_SEAGATE&PROD_EXPANSION\7&171E92E2&0&000000"
Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available"
SCSI Bus:"0"
SCSI LUN:"0"
SCSI Port:"2"
Sectors - Per Track:"63"
Sectors - Total:"3907024065"
Serial Number:"NA8RW3BD"
Size:"1.82 TB"
Size – Available:"882.76 GB"
Status:"OK"
Tracks - Per Cylinder:"255"
Tracks - Total:"62016255"
- "F:"
Availability:"Not Available"
Caption:"F:"
Compression Method:"Not Compressed"
Description:"Local Fixed Disk"
File System:"NTFS"
Name:"G"
Serial Number:"883BD475"
Size:"976.56 GB"
Size – Available:"474.15 GB"
Status:"Not Available"
Volume Dirty:"No"
- "H:"
Availability:"Not Available"
Caption:"H:"
Compression Method:"Not Compressed"
Description:"Local Fixed Disk"
File System:"NTFS"
Name:"BACKUP2"
Serial Number:"92C9D18E"
Size:"886.45 GB"
Size – Available:"408.62 GB"
Status:"Not Available"
Volume Dirty:"No"
...#SSU#...
#Logs#System Messages#Included
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WinDefend service.
-------------------------------------------------------------------
Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2a119cd1-9fa1-4045-ac74-54fdc322464f}, had event Fatal error: The miniport has failed a power transition to operational power
-------------------------------------------------------------------
The Bluetooth driver expected an HCI event with a certain size but did not receive it.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Bluetooth driver expected an HCI event with a certain size but did not receive it.
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NCBCSZSJRSB-SpotifyAB.SpotifyMusic.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
-------------------------------------------------------------------
Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2a119cd1-9fa1-4045-ac74-54fdc322464f}, had event Fatal error: The miniport has failed a power transition to operational power
-------------------------------------------------------------------
Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2a119cd1-9fa1-4045-ac74-54fdc322464f}, had event Fatal error: The miniport has failed a power transition to operational power
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2a119cd1-9fa1-4045-ac74-54fdc322464f}, had event Fatal error: The miniport has failed a power transition to operational power
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Energy Server Service queencreek service terminated unexpectedly. It has done this 2 time(s).
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
-------------------------------------------------------------------
The server {B8C1DCAE-5020-4F5D-BA2A-85292744E334} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {1F18FC75-A353-4121-AEDB-19DF9C98F622} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Bluetooth driver expected an HCI event with a certain size but did not receive it.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {B8C1DCAE-5020-4F5D-BA2A-85292744E334} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s).
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {B8C1DCAE-5020-4F5D-BA2A-85292744E334} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {1F18FC75-A353-4121-AEDB-19DF9C98F622} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Apache Tomcat 10.1 Tomcat10 service terminated with the following service-specific error:
The system cannot open the file.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80240017: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.409.651.0) - Current Channel (Broad).
-------------------------------------------------------------------
The GoogleUpdater InternalService 126.0.6441.0 (GoogleUpdaterInternalService126.0.6441.0) service terminated with the following service-specific error:
%%45
-------------------------------------------------------------------
Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2a119cd1-9fa1-4045-ac74-54fdc322464f}, had event Fatal error: The miniport has failed a power transition to operational power
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Bluetooth driver expected an HCI event with a certain size but did not receive it.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The driver detected a controller error on \Device\Harddisk1\DR1.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The driver detected a controller error on \Device\Harddisk1\DR1.
-------------------------------------------------------------------
The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {9A4948D9-13FC-4FAC-B60A-FBA6EE0FB11C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {1F18FC75-A353-4121-AEDB-19DF9C98F622} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {B8C1DCAE-5020-4F5D-BA2A-85292744E334} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {B8C1DCAE-5020-4F5D-BA2A-85292744E334} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {1F18FC75-A353-4121-AEDB-19DF9C98F622} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {B8C1DCAE-5020-4F5D-BA2A-85292744E334} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The driver detected a controller error on \Device\Harddisk1\DR1.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
DCOM got error "1053" attempting to start the service DevicesFlowUserSvc_3db3a with arguments "Unavailable" in order to run the server:
DevicesFlow.DeviceDiscoveryAndPairingBroker
-------------------------------------------------------------------
The Secure Socket Tunneling Protocol Service 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 DevicesFlowUserSvc_3db3a service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the Secure Socket Tunneling Protocol Service service to connect.
-------------------------------------------------------------------
A timeout was reached (30000 milliseconds) while waiting for the DevicesFlowUserSvc_3db3a service to connect.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Windows Biometric Service service did not shut down properly after receiving a preshutdown control.
-------------------------------------------------------------------
The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control.
-------------------------------------------------------------------
The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NKSQGP7F2NH-5319275A.WhatsAppDesktop.
-------------------------------------------------------------------
The driver detected a controller error on \Device\Harddisk1\DR7.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
-------------------------------------------------------------------
The driver detected a controller error on \Device\Harddisk1\DR7.
-------------------------------------------------------------------
The GoogleUpdater Service 126.0.6441.0 (GoogleUpdaterService126.0.6441.0) service terminated with the following service-specific error:
%%45
-------------------------------------------------------------------
The GoogleUpdater InternalService 126.0.6441.0 (GoogleUpdaterInternalService126.0.6441.0) service terminated with the following service-specific error:
%%45
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MZ95KL8MR0L-Microsoft.ScreenSketch.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NKSQGP7F2NH-5319275A.WhatsAppDesktop.
-------------------------------------------------------------------
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone.
-------------------------------------------------------------------
The Bluetooth driver expected an HCI event with a certain size but did not receive it.
-------------------------------------------------------------------
The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s).
-------------------------------------------------------------------
The GoogleUpdater InternalService 126.0.6441.0 (GoogleUpdaterInternalService126.0.6441.0) service terminated with the following service-specific error:
%%45
-------------------------------------------------------------------
The GoogleUpdater Service 126.0.6441.0 (GoogleUpdaterService126.0.6441.0) service terminated with the following service-specific error:
%%45
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the HPAppHelperCap service.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {2a119cd1-9fa1-4045-ac74-54fdc322464f}, had event Fatal error: The miniport has failed a power transition to operational power
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The server {1F18FC75-A353-4121-AEDB-19DF9C98F622} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {B8C1DCAE-5020-4F5D-BA2A-85292744E334} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The driver detected an internal driver error on \Device\VBoxNetLwf.
-------------------------------------------------------------------
The driver detected a controller error on \Device\Harddisk2\DR2.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The driver detected a controller error on \Device\Harddisk2\DR2.
-------------------------------------------------------------------
The driver detected a controller error on \Device\Harddisk2\DR2.
-------------------------------------------------------------------
The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The driver detected a controller error on \Device\Harddisk2\DR2.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
-------------------------------------------------------------------
The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout.
......
FILE TRUNCATED
Please see attached file for complet version
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, cvmontuy.
I appreciate your efforts in providing and sharing the SSU logs here.
Could you please confirm if the external LG monitor with a resolution of 2560 x 1080 previously functioned properly on your HP laptop with Iris Xe Graphics? Additionally, have there been any recent modifications to the system prior to the onset of this issue?
We suggest trying the Display Driver Uninstaller (DDU). You can find instructions on how to use it in the guide titled "How to Use the Display Driver Uninstaller (DDU) to Uninstall an Intel® Graphics Driver." After running the tool, it's advisable to install the latest driver from HP first. Utilizing drivers provided by the computer manufacturer is recommended initially. If the problem persists, consider performing a clean installation of our latest driver.
Furthermore, could you please provide us with the Intel Graphics Driver report? You can generate this report by following these steps within the Intel® Graphics Control Panel or the Intel® Graphics Command Center.
Looking forward to your response. Have a nice day!
Best regards,
Von M.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The LG ultrawide external monitor works fine when connected to an old Dell G3 laptop with Nvidia graphics card.
However, on the HP laptop purchased about a month ago, it never utilizes the 2560x1080 resolution of the LG monitor; it only takes the 1920x1080 resolution.
On the HP site, we could find three drivers, two for Intel and one for Nvidia. I have been using the latest Intel driver from there, but it never utilizes the full resolution.
I just installed the latest Intel graphics driver on the HP laptop, but it still does not recognize the 2560x1080 resolution of this LG ultrawide monitor.
Attached, you will find the graphics driver report.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, cvmontuy.
Thank you for providing detailed information about your issue. Since your LG ultrawide monitor works fine with the old Dell G3 laptop but not with the new HP laptop, it seems to be a driver or configuration issue specific to the HP laptop.
Here are a few steps you can try to resolve this:
- Check the Display settings: Make sure that the display settings on your HP laptop are set to the correct resolution (2560x1080). Go to Settings > System > Display and manually set the resolution if it's not automatically detected.
- Update BIOS and Chipset Drivers: Sometimes, updating the BIOS and chipset drivers can resolve compatibility issues. Check the HP support site for any updates. Moreover, please be guided that we have the latest graphics driver update from our Intel Iris Xe Graphics website.
- Check Cable and Ports: Ensure you're using a high-quality HDMI or DisplayPort cable, and try different ports on both the laptop and the monitor. Intel® Iris® Xe Graphics can support ultrawide display resolutions using DisplayPort (DP) 1.2 connections or newer. However, the resolution on the External Monitor is Limited to 1920 x 1080 or 1900 x1200 Using HDMI.
Please let us know if these steps help or if you need further assistance. If the issue persists, I recommend reaching out to HP support for more specific troubleshooting related to your model.
Best regards,
Von M.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks a lot about you support:
The HP Laptop does not offer the option for 2560 x 1080 with any of the different drivers that I have used, the max resolution available on windows 11 for this monitor is 1920x1080.
The laptop BIOS and chipset are up to the latest version published by HP for this model.
I got a brand new HDMI cable certified for high speed. Neither the HP laptop nor my monitor has a DisplayPort, only HDMI.
Now I am using the resolution 1920 x 1080 on this monitor. It is not optimal, but it works. I am thinking of getting a new laptop in a couple of months, one from ASUS or Lenovo. I definitely won't recommend the HP brand for laptops anymore.
Thanks again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello cvmontuy,
I wanted to check if you had the chance to review the information we posted. Please let me know at your earliest convenience so that we can determine the best course of action to resolve this matter.
Best regards,
Norman S.
Intel Customer Support Engineer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks a lot,
Please review my previous post.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page