I have noticed on this and other threads on the subject that the process does not seem to work well when it comes to integrated graphics cards found on a laptop computer. 

Laptop computer graphics cards do not usually have the generic Hardware IDs the generic AMD/ATI driver from the AMD site expects, so the driver will not install.

There is no workround for AMD drivers. The only possible solution is to install the best available driver for the laptop model (from the laptop manufacturer's site) in compatibility mode.

I agree!  I am 'flipping' between Win 10 and Win 7 (I only have one computer, but I spent 25 years doing support :) ), and the machine runs just fine using the 14.9 driver.

Something that hasn't been mentioned in the last few posting is that this driver also cured the 'missing letters' problem that plagued Win 10 for a lot of people.

Personally, I'm having a lot of fun 'playing' with this 'new version'!

Finally got a driver installed and screen up to 1280x800 proper default for the attached display.

Downloaded R168685.exe from Dell

Set compatibility to Vista

Ran to extract, exited when catalyst installer got stuck on looking for components

Started Device Manager

Went to Display Adapters/Windows Basic Display

Update Drivers

Browse my Computer for drivers

Pointed to C:\Dell where they had been extracted to.

Next

So I have just installed windows 10. Everything seems to be working ok, if a little slow. The only problem seems to be the driver for my AMD Radeon HD 8400. After having a few gos at installing the latest catalyst drivers via the auto detect utility I am still getting 'Windows has stopped this device because it has reported problems. (Code 43)' in device manager. I am also getting a message from catalyst on load saying the device isn't working.

Anyone have a work around?

Is it worth trying out the AMD Clean Uninstall Utility?

Thanks.

This is a problem with the latest build of Windows 10.

The Windows Feedback application lists quite a few people complaining about this and there doesn't seem to be a solution to it at the moment.

I had this problem with a radeon mobile 8240 and had to roll back. It returned to the previous build of win 10 and functions again.