This week my 16:9 monitor will only work on 4:3 and there is no longer the option in windows to choose 1920x1080
This week my 16:9 monitor will only work on 4:3 and there is no longer the option in windows to choose 1920x1080
The same happened to me with my HD 4600 yesterday following a Microsoft system update. I understand that AMD not longer supports the 4000 series. I did read a message from someone on this site who had a similar situation a while ago and found that using a 5000 series driver cured the problem Unfortunately I can't find that message now that I have taken the first step in his suggested fix, which is to use AMD's driver to purge the PC of previous drivers. I'll get back if I find that message again.
Here is the driver I believe you need for your HD4000 series, but you may also want to go to your laptop manufacturer site and download the driver from there first, especially if you have an HP Laptop
Here is the AMD Catalyst Legacy Driver I think you need:
AMD Catalyst 13.1 Legacy Download
I was unable to find the above driver using the AMD Drivers Download Page ... so I pointed you elsewhere.
More information / background below - top one is most relevant to you I think.
Driver Support for AMD Radeon™ HD 4000, HD 3000, HD 2000 and older Series
AMD Radeon™ Software Support for Legacy Graphics Products
AMD Radeon Software Crimson Edition 16.2.1 Beta for Non GCN Products Release Notes
FYI on Windows 10 Pro Fall Update (17.09) there are now options to defer Updates, Only Apply Security Updates, and select which update branch you are on.
That may be a better option than completely disable driver updates.
Best option of course is to stay on Windows 7 or roll back to Windows 8.1 if you can until you move to Linux...
Hope this helps you out anyhow.
Bye.
I got my old configuration back. With the last Windows 10 update, the same picture came up on both of my monitors and the highest resolution I could get was 1600x1200 so images were inflated horizontally. Also, although both screens were working, Windows only recognized one of them. It looks as if the Windows update trashed all of the relevant drivers and installed default, generic drivers.
All is well again. After trying to get various driver combos to work, I did what I should have done at the start, which was:
Hi,
Thanks you itma, now it's ok !!!