Update shipped for Windows 10 version 1703 and 1709

Dec 19, 2017 12:40 GMT  ·  By

Microsoft has released a new Windows 10 update for systems running the Creators Update (version 1703) and Fall Creators Update (1709) in order to fix issues with faulty AMD graphics drivers.

Update KB4057291 is only aimed at systems with AMD legacy cards running drivers version 22.19.128.0, which apparently causes a number of issues on these computers, including support for only three resolutions, no matter the monitor and graphics card settings.

As GHacks notes, only three display resolutions are being offered after installing the latest driver version, namely 800x600, 1024x768 and 1280x1024, and rolling back to a previous driver was the only way to deal with the problem.

This update, however, should correct this unexpected behavior, according to Microsoft’s knowledge base article published on December 18.

“Multi-monitor display and display resolution are not working for some AMD legacy cards (for example, Radeon HD 2000, HD3000, and HD4000 series) that mistakenly receive driver 22.19.128.0,” the company explained. “This update will install a driver to restore multi-monitor display and resolution control capabilities.”

Shipped via Windows Update for AMD systems

This update is available via Windows Update for systems with AMD legacy cards, but at the same time, it’s also published on the Microsoft Update Catalog should system administrators want to install it manually. A reboot is recommended after installing the patch.

Computers were Windows Update is configured to automatically install updates might have already received the patch and the issue is corrected. To check if the patch was deployed, launch the Settings app and head over to Update & Security > Windows Update > View installed update history and look for KB4057291 in the list of installed updates.

There are no reports of failed installed and patches like this typically deploy correctly, but we’re still waiting for confirmation to see if the graphics driver issue is indeed fixed on all systems that previously experienced the unexpected behavior limiting resolution settings.