Unsolved

1 Rookie

 • 

2 Posts

 • 

7 Points

32

June 2nd, 2026 11:43

Windows nuked the device tree and display died... sorta

I wanted to make Dell aware of this....
I deleted the driver for my external monitor to troubleshoot an HDMI audio issue; it was intermittently failing for some reason. When I did this, MS in their infinite wisdom, nuked the whole device and sub-tree. This (apparently) also removed the laptop display driver, but also put it in a bad power state or something. After this, the display would not display except in bios. As soon as Bios handed things over to the OS, the display would no work (except once it flickered the login screen for about 250ms) and no amount of rebooting, shutting down or device rediscovery would work; It was GONE FROM THE DEVICE TREE.  So, how did I fix it?

The night before I was going to take my computer in I happened to decide to make my life a little easier by shutting my computer down and leaving it overnight. This fixed the issue and this is why I conclude it was in a weird power state. Bios was able to recognize it, windows was not. I've since learned that BIOS addressed the hardware more directly and windows uses ACPI enumeration, which was failing because of the unsafe hardware state that wasn't cleared by either windows or BIOS or by rebooting or shutting down.

I will admit that this isn't exactly the Dev's fault, because windows shouldn't have murdered the whole device sub-tree, but this is an issue severe enough that it could legitimately cause less knowledgeable users to return their hardware. I myself was about to reimage the thing, which, had I left it plugged in overnight, would NOT have worked or resolved the issue, and would have led to a dell hardware replacement and needless $$ for dell.

This would probably also have been resolved by draining flea power, but a lot of techs wouldn't think to do this... I would have, if there was a way to do it without disassembly, DELL, but you didn't provide a means for this. I'm annoyed at that.

This is admittedly an edge\corner case but I think it's enough to warrant a couple days of dev time.

Model: Dell Precision 3560

What Was Confirmed:
Intel GPU driver files intact in DriverStore (oem27.inf / iigd_dch.inf v32.0.101.7084)
No missing or corrupt driver files
External monitor (Acer, NVIDIA T500) working normally
Laptop panel shows no backlight glow  no signal at hardware level
Safe Mode: laptop display still dead (rules out driver stack issue)
pnputil /enum-devices /instanceid "PCI\VEN_8086&DEV_9A49" /relations returns nothing

What Was Tried:
Shutdown and reboot
Dell Command Update / full driver CAB
DISM /Online /Cleanup-Image /RestoreHealth
pnputil /remove-device /subtree + /scan-devices (multiple attempts, normal and Safe Mode)
Manual DriverStore INF pushes
Windows Update / Optional Updates
Hibernate for 2 days without power (the weekend)

Oh, and to be clear, everything appears to be working now after days of this not working.

Requested resolution is that BIOS re-initialize this hardware on boot.



10 Wizard

 • 

17.7K Posts

 • 

70.7K Points

June 2nd, 2026 21:26


everything appears to be working now after days of this not working.



Good and thanks for the report.

 

I would have tried Windows Safe-Mode, or maybe trying to get the F12 ePSA Diags.

Also maybe try booting a flash drive (Windows Installer, Macrium Reflect Rescue, Ubuntu Linux Trial/Demo, etc.)

Good work and glad to hear you got it running again.

1 Rookie

 • 

2 Posts

 • 

7 Points

June 3rd, 2026 14:29

I did actually try windows safe mode, but even that environment wouldn't display on the laptop display because the hardware was in an unsafe state that was preventing it from initializing during ACPI enumeration. Also, because of yellowkey (the bitlocker pwnage) bios access has been fully disabled by the device administrator. I work in IT, but not in Endpoint so I didn't wanna mess with the apparent workaround.

No flashdrive would've booted. The next step was windows reimage, but still, If I hadn't left it unplugged and shut down overnight, the hardware would have been stuck in that bad state. The one and only resolution would have been to fully discharge the residual static charge in the capacitors that was maintining the unsafe hardware state. I suspect that even booting to linux or any other rescue disk would prove just as futile as it would still use similar methods to perform ACPI enumeration. 

Had I initially pulled the battery (by disassembling the machine) and held the power switch, I'm 99.8% sure that would have resolved the issue caused by windows unsafely killing the device.

No Events found!

Top