AMD chipset not recognised

[keith with the teef]

Strange. I decided to get the latest chipset drivers for my media center: B450, athlon 200ge.

Only to have the installer think my machine was something other than amd and so exited.

huh?

Anyway, I looked through device manager and M$ seem to have all driver covered with there generic.

The machines hardware works fine with no lag or crashes. So I guess all,s well.

I guess the superdooper uninstaller I used cocked up.

[Ed P]

I think that you are probably correct, the system already had the best firmware installed,

I have however noticed one thing associated with my habit of always running as a ‘user’, and just temporarily promoting to Admin for installations. This works perfectly for 90% of things, but driver installs just fail silently unless I log into a full Admin account and run the install from there.

[Wheels-Of-Fire]

Installers shouldn’t really fail silently these days. Ever since Vista, a programs manifest should have an entry that says whether it requires elevation and that should produce a UAC dialogue box.

However, if you do come across a rogue program then it may still be worth using “Run as administrator”, even if you are logged in as an admin.

The reason is that, since Vista, admins normally run with a standard user security token and only switch to their admin token when requested by UAC or by using “run as”.

Processes also inherit their token from their parent so if you launch a program from an elevated command prompt then it will also run elevated.

Sorry if i’m stating the obvious to some people 😁

[keith with the teef]

Hmm. I have checked user account and I am am the administrator. I think the uninstaller I used may have put a lock on the drivers package. I will try unlocker tomorrow. If I can get my hands on it.

[Author]

Posts