I have had the problem for 1-2 months that the display of my Asus notebook broke. But since I still had a monitor at home, I could now easily connect the laptop to the monitor via HDMI and also got a picture.
However, a few hours ago I updated the drivers of the AMD graphics unit and since then I have not been able to get an image on my monitor. I have already tried the hotkeys "Win-Key + P" and also the shortcut "[FN] + F8", but neither worked. Unfortunately, I don't see anything on the display anymore, but when I use the hotkeys, I see on the right edge how the display gets a little brighter, but as I said, I can't see anything. Is there anything else you can do or is there nothing more to do than replace the display?
Well don't update graphics drivers if the old ones spark. There have been problems like this many times.
The problem seems to be within the graphics. Take something bootable and plug it in, and start again.
If it doesn't work then it's the display.
Yes, I also think it's because of the drivers, but it doesn't explain to me why I still can't connect the hotkeys or shortcuts to an external monitor, neither my TV nor my monitor. What do you mean by "something bootable"?
Well eg a Windows boot CD or a boot stick. Whatever you are doing, you can test whether it is in the system in the hard disk or there's damage to the hardware.
In the bios you can usually deactivate the internal display and set "default external" for such eventualities. I mean that you can completely disable the internal monitor in many bios. Alternatively, you could connect a USB graphics card and try to get it up and running with the internal graphics card.
in safe mode you can kick the internal monitor driver, so that only one monitor is explicitly recognized when booting, the external one.
the WIN P does not work but because something changes on the monitor, it can be concluded that you could even set the default display to 1 instead of 0 via the registry and maybe something will work again, but the latter would be a little bit more effort that I would not do at first recommend. In safe mode, however, this would be the first point of contact - because there the monitors are usually duplicated and not expanded.
You could try to get to the PCs via rdc. Can only work if this has already been released.
Is the first method possible without me being able to see anything on the display? If so, could you possibly explain to me in more detail how I do this? If I'm not experienced in the field, unfortunately. I have an Asus F555B laptop with Windows 10, if that helps you somehow. But thanks for your answer!
Unfortunately I don't know exactly what an "rdc" is, could you explain that to me in more detail?
Ne without looking at windows is not a lot to do, especially if you are not very knowledgeable.
Sure, you can do that via powerShell without looking, if you can already do it, but as a rule the safe mode would be the most solid decision to move around. The bios is usually still the best choice, simply make the internal monitor, connect the external one and then when booting up the wonder'ws only recognizes a monitor like any other pc that has an internal graphics card on the mainboard and directly with it connected to the monitor.
what you can see is whether your lappi has 2 outputs. In the default mode, only the VGA adapter is activated, the dog may already be buried in your paradigm.
Otherwise just order a cheap USB graphics card - configure your windows accordingly and deliver the ext-graphics card back, your right to cancel the purchase if it was at a distance.
Remote desktop connection - remote access / remote maintenance / request remote support / teamviewer / screensharing / Remote Access Service
But will not work - a default user is not an admin and a default admin has no password - so far, a "user level" account can't verify for the firewall around the UDP without any RDC verification of a higher level open or let open to build the tunnel. Ergo, you first have to generate an invitation in the settings that includes the auth token for verification. Without looking - and without you being able to do that, there's nothing to tickle out of a normal user account. If you are logged in you must first activate the screen reader in the locked mode - then you have to press WIN + pause, listen and press 4 times tab - then space bar then 3 times tab then space bar then listen and again tab or two times. And so on. At the end you send this to an email address that you can access remotely at a terminal or desktop and then you can slowly think about assigning a valid password to the admin via SSH, then log off powershell the user and log on admin - the then at the desktop session, then disconnect the whole thing from SSL, throw on your favorite "desktop software" on the local PC and then access the Windows RDC remotely. The screen remains black anyway if you don't have a PRO installed. Which is probably not the case on a laptop.
or again: safe mode - that saves a lot of fiddling and is native VGA!
In fact, I connected the monitor via HDMI, but I don't get any image on my external monitor via VGA either. Safe mode can be started via Shift + F8 right? I've already done that, but to no avail. I just wonder why it didn't work overnight after I updated the graphics unit driver.
The new drivers require high graphics settings and configurations.
they are usually not optimized for "fallBack" and VGA and such old-fashioned bells and whistles, but more or less for "digital media" that come from the modern.
it may be that your monitor is just being controlled with HDMI + 60 but in reality only swallows max 51hz - zack says its mainboard that it remains black and only the backlight was forgotten during the developement to fit on the FW and already that flickers at certain values, but for "security" the displa remains black.
I say secure mode actually has to check that, it has sVGA resolution with 30 frames / s and 16k colors.
But let me tell you one thing: last time I saw windows at work last night, otherwise I haven't been using wonderw's for more than 10 years because some details bother me.
You have to dive an instance deeper and look in the bios that you are killing the internal screen "kind justice" from the whole thing. Otherwise win-smart will not get ahead with you and your ideas.
I will report again, I actually got it to work, but on a rather harder way. I plugged the display connection cable from my laptop into the motherboard and connected my monitor via HDMI, which apparently recognizes the monitor as the main screen.
Great if that is not killed properly - perfectly thought of you.
In the next step I would first screw the graphics down completely and then reconnect the internal screen and then work up to the max resolution step by step. As long as it says "you want to keep the settings 10… 9 .8 .7" nothing can happen I think.
I just looked, the manufacturer of my graphics card writes a maximum of 1080 resolution, there's nothing more.
hmm, now I have linux and.