Has anyone had any luck extracting AMD chipset drivers from amd_chipset_software.exe?

Z

ZorkLVM

Member
Messages
47
Reaction score
4
I've tried everything, including asking for help from a bunch of AI's.

Have you had any luck extracting so you can integrate into your NTLite iso? If so, how did you do it? Which tools did you use?

The attached pic is as far as I've gotten, but I don't think it's right. I think there are files missing.

View attachment 13493
 
Not sure if it will help, but I just installed the amd chipest drivers for b650e through the exe(Amd_chipest_software) after extracting first with 7zip.
It gave me a option to choose between: 3D_v-chache_performance, gpio2, i2c,interface,psp,pmf. I only installed gpio2 and i2c since it indicated that I only had those with older version on fresh windows install.
 
Thanks for the info, @quo. AMD obfuscates the heck out of their chipset driver package. What you're looking at above is a .msi inside of an .exe inside of an .exe.

There are some issues integrating the as-is output into NTLite, depending on whether you're integrating into Win10 or Win11.

I think I've got it hammered out now, but if anyone has a bulletproof way they've been doing it, I'd love hear.
 
ZorkLVM said:
I think I've got it hammered out now, but if anyone has a bulletproof way they've been doing it, I'd love hear.
Click to expand...
I just run the Exe, and go to C:\AMD\Chipset_Software\Packages\IODriver. If you want to select just the drivers for your machine, load up Vanilla windows and go to the Drivers tab, then put all of those subfolders into NTLite and click "Remove Unused Drivers" (or however it is spelled in English? Mine is in PT-BR), It'll auto-remove everything not used by your machine (you can also do it for another machine by loading a HWList), then copy those driver files NTLite is keeping to a separate folder.

As an example here's the AMD Drivers folder vs just the driver files of one specific machine I use (so just the GPIO2, I2C, INTERFACE, MicroPEP, PPMPF, PSP and SMBUS folders):

View attachment 13514 View attachment 13515
 
I just run the Exe
Click to expand...
Thanks but the exe refuses to run on non-amd hardware. I haven't discovered any flags for the exe.

The legacy chipset installer extracts the way you describe just fine.
 
h
ZorkLVM said:
Thanks but the exe refuses to run on non-amd hardware. I haven't discovered any flags for the exe.

The legacy chipset installer extracts the way you describe just fine.
Click to expand...
hmm thats interesting, because i rolled the amd chipset drivers along with a stack of other intel equivs into one of my images and when you install it on an intel machine - the amd chipset drivers and all the associted services come installed, same with the processor support that come packaged with the chipset drivers like the vcache service. its annoying because the way they get rolled into the image bypasses the normal "only install on supported hardware" check that are built into the installer packages. in the vice versa case - i have an amd rig that is running all of the services for intel management engine.

fyi:
try running the driver installer from a cmd line with the "/?" switch, quite a lot of driver packages actually have a switch that creates an unattended installer package and by invoking the help switch they often give you the switch options.
 
As you want to integrate these drivers maybe you got a PC that needs these drivers and is able to install these drivers.
So setup this PC with a clean image and install these drivers. Then export these drivers (i use DISM++) to get a folder with all needed files. After that you can integrate with NTlite.
 
What chipset version.... I have the latest extracted,


ZorkLVM said:
I've tried everything, including asking for help from a bunch of AI's.

Have you had any luck extracting so you can integrate into your NTLite iso? If so, how did you do it? Which tools did you use?

The attached pic is as far as I've gotten, but I don't think it's right. I think there are files missing. What chipset? I have the latest extracted already

View attachment 13493
Click to expand...
 
A little bit late but I succeeded extracting .msi and .cab files from "AMD_Chipset_Drivers.exe".
Here is the process (intel or AMD platform does not matter):
1. Download chipset installer from AMD.
2. Open exe file with 7zip or any extractor and within that file grab AMD_Chipset_Drivers.exe.
3. Open "C:\Users\USERNAME\AppData\Local\Temp" folder and keep it open.
4. Run "AMD_Chipset_Drivers.exe" (Do not close if any error message pops up) and look at "C:\Users\USERNAME\AppData\Local\Temp" folder
5. Copy newly created "{2018E0FE-C33A-4250-AF78-3DE16D09911D}" (or similar named) folder somewhere else.
6. In that folder you will have the msi and orginal exe installer.
7. You can further extract msi file to a folder for cab file which contains all the drivers.
You can see pictures below.
 

Attachments

  • 1.PNG
    1.PNG
    21.4 KB
  • 2.PNG
    2.PNG
    51 KB
  • 3.PNG
    3.PNG
    40.6 KB
  • 4.PNG
    4.PNG
    79.1 KB
  • 5.PNG
    5.PNG
    119 KB
Last edited:
Here are the 2 methods I prefer for extracting, exporting, optimizing, and integrating drivers:

I currently own a mini PC with a mobile AMD processor, an Intel integrated laptop, and a custom built Intel desktop computer. I explored all my options on how to cleanly integrate the smallest footprint of drivers, without any OEM bloat, extra helper add-ons, and so forth. Anyone that does this level of tweaking on laptops or mini PC knows how much of a pain this can be, because mobile and laptop chipsets have so many more drivers than a desktop (almost double.) These drivers include some mandatory ones, but also a ton of bloat, ads, and helper services disguised as necessary. The optimal method I settled on is to follow the steps in the spoiler (link) of one of my previous posts. This works for all drivers as far as I know.

I'll also help clarify this thread for people that want to go the traditional route of extracting executables. For that approach, use 7Zip to extract a driver executable file to see its contents. Next, load NTLite and in the drivers section there is the ability to point to an INF file which tells NTLite to gather all files that would normally be installed if you manually ran the driver at the desktop after reinstalling Windows, and then NTLite saves those for integration. The optional, but most critical step, is to click the "Remove unused" button, which tells NTLite to get rid of any drivers that do not belong to your specific computer hardware. In other words, that button helps eliminate bloat. It is still not as effective as the approach I explain in the link above, but the NTLite method is easier, faster, and better than how I see most people do it so it's a great choice too.

As an example of what these two methods accomplish, I currently have a gaming setup on the mini PC for my kids which has no optional GPU software running, no helper apps like driver assistants or anything similar, and it has no extra services belonging to any driver that isn't necessary for critical operations. There will still be things that need to be disabled in other ways, but these approaches provide optimal baselines for integrating drivers.
 
Last edited:
You must log in or register to reply here.
Back
Top