One I encountered recently. It was my fault, but I fixed it. Here are the circumstances. I realized there are two actual solutions (probably more if I have better software tools). But this was fixed within an hour
Initial circumstances
Laptop Windows 10 64-bit UEFI
Was stepped on, lid and bezel are permanently damaged, and unable to find replacements. Display is heavily damaged. Display cable is damaged.
You manage to get it up by plugging it into an HDMI cable. Screen is of course blank since it will always init to the lcd screen, until windows boots
You realize you need to uninstall an adobe service that won't let you unload it.
You set it to minimum safe mode
You realize with the generic driver, it will never switch over to the monitor
I realized later I could go through the msconfig gui in my head. But I used another way. I'm curious what you come up with
(does not involve getting the lcd screen to work)
Initial circumstances
Laptop Windows 10 64-bit UEFI
Was stepped on, lid and bezel are permanently damaged, and unable to find replacements. Display is heavily damaged. Display cable is damaged.
You manage to get it up by plugging it into an HDMI cable. Screen is of course blank since it will always init to the lcd screen, until windows boots
You realize you need to uninstall an adobe service that won't let you unload it.
You set it to minimum safe mode
You realize with the generic driver, it will never switch over to the monitor
I realized later I could go through the msconfig gui in my head. But I used another way. I'm curious what you come up with
(does not involve getting the lcd screen to work)
Comment