Ati Radeon Hd 4350 (microsoft Corporation Wddm 1.1) Driver _BEST_ Download
Almeda Mithani
Does anybody know, is there a way to make Radeon HD 4350 WDDM 1.1 driver (ver. 8.970.100.9001) to appear dumber than it is and let OS think that it simply does NOT support H.264 hardware-accelerated decoding (much like it does not H.265)?
ati radeon hd 4350 (microsoft corporation wddm 1.1) driver download
Download File ===> https://t.co/DtlPtzY1xB
Troubleshooting another issue ( -flickering-aom-patch-2-7-4511863-wddm-1-1-directx-12-featur...) I downloaded previous version 8.970.100.7000 of the driver from AMD web-site, for Windows 8 x64 ( -radeon-hd/ati-radeon-hd-4000-series/ati-radeon-hd-4350).
The reason i bring this up is that one of my occupations is IT for several companies and personal computers, and over the weekend i've been inundated with numerous calls and complaints after many of these machines running HD4000/3000/2000 series graphics cards without issues at all since windows vista/7 and majority of which received the update to windows 10 and took it without a problem since it first launched, using their HDMI connected tvs and multiple displays in some situations without a problem and even playing many games without fault. Sadly this has changed and there doesn't seem to be any other explanation that something one microsoft's update server or dumped into the creators updates have royallyed screwed things up. Hell just writing this post up i've received an additional 3 calls, and there isn't any real easy solution to implement. One would think extracting the 13.4 beta or 13.1 WHQL driver and manually force installing it would work, but the installer or windows driver installer itself reports "successfully installed" followed by no change in driver version in the devices properties or it's status even after numerous reboots.
Out of curiosity i performed a clean install on a machine with a HD4350 I happen to have on hand along with another with a HD4870 1GB.... and the results are identical, the improper driver is loaded by default, failing to load appropriate display resolutions and showing "no driver". I'm sure there may be exceptions out there, but so far i haven't found them.
Currently on this same machine, i'm performing the 1709 update straight from 1607 to see what ends up occuring with the proper 9001 microsoft supplied driver active and running. My hope is that the 1709 will install and that the updates won't attempt to install a new version again, however if it does, again the hope is that the original 9001 will remain.
On a Windows 10 version 1607 containing a 2400 Pro, while the "rollback" driver was unavailable, manually updating the driver and selecting from a list showed 3x of the incompatible driver along with the original 9001 driver that had been previously used followed by the microsoft VGA driver. Selecting the 9001 and then proceeding worked fine. After which i manually started a 1709 installation via a usb flash drive with the full 1709 installer on it, from within 1607. When asked if I'd like to search for new updates within the setup for 1709, i declined and proceeded. Once 1709 had completed the installation, the wrong driver was once again installed, however again i was able to go into device manager and repeat the steps to install the 9001 driver without issue. I'm going to leave this machine running overnight and play around with it for the next couple of days with 1709 to see if the improper driver attempts to install again. In the mean time I'm having no luck getting the 9001 driver to be installed (as it's provided by microsoft's update but doesn't appear to be providing it any longer), nor will a manual install of the 13.4 or 13.1 whql driver on a clean install of 1709.
Regarding 2 machines i've now worked on, both the windows 1607 and 1511 that had their drivers replaced via an update without the ability to directly roll back, I've managed to successfully roll back in the way i explained above, manually do the 1709 update directly, and then repeat the step to recover the 9001 driver and install. I'll report back if i can get a clean install to function properly. I'm thinking it would be wise to extract the 9001 driver from the driverstore and pack it up, uploaded to the internet and share it if microsoft doesn't change the update. In the meantime, i've left the one machine overnight and have since performed several restarts and other updates and the 9001 doesn't appear to be getting replaced. For the time being this seems like the best solution IF it's available for you.
Outside of managing to get the 900 driver (officially amd/ati release) instead of the 9001 (microsoft supplied) to install on some clean installs now that it appears that microsoft is no longer forcing the improper one to install but failing to install the 9001 still, things seem to be running smoothly with the 900.
356178063d