AMD Chipset Driver 3.10.22.706 Won't Install

Mortiferon said:

Oh boy... DISM missed whatever that was (will be adding SFC to my batch file).

OK. I will be attempting to install 3.10.22.706 now...

Edit: Nope! Now truly lost in the woods here. I really don't want to have to freaking Clean Install 10 right now. (And I haven't even really been doing much on here to explain why there'd be such bad corruption, damnit).

You don't have to do a clean install. You can do an In-Place Upgrade... it only takes about 40 mins total.
This will repair Windows, but leave your programs and files untouched.

Repair Install Windows 10 with an In-place Upgrade



Here is the short version of the In-place upgrade tutorial...

DISABLE non-Microsoft:
a) antivirus software
b) firewall software
c) drive encryption software

Make a full OS backup with a program like Macrium Reflect (free)
Macrium Software | Macrium Reflect Free

Go here and get the Media Creation Tool and save it to your desktop.
https://www.microsoft.com/en-us/soft...load/windows10

RUN the Media Creation Tool and use it to: Create an ISO image... save IT to your desktop.
This will be the latest version of the ISO image.




Right click the ISO image and choose: MOUNT
Open File Explorer and you will see a new drive letter. It will "look" like a DVD optical drive.
Double click the new drive letter to open it.
Find setup.exe and double click it to start the in-place upgrade.

Choose the Keep personal files and apps option.

After it's all done... to UNmount the ISO image, right click the new drive letter and choose: EJECT.


The ONLY thing you will lose is some of your personalizations. Your programs and data will be intact.

Mortiferon said:

OK! I do believe I've resolved the problem:

Temporarily killed Defender (Windows Security > Virus and Threat Protection > Manage settings > uncheck ALL, yes, blah blah)

I put back my original C:\AMD folder.

C:\Program Files (x86)\AMD\Chipset_Software

AMD_Chipset_Drivers.exe

Ran that as Administrator. Install.

Now:

And back in Progs/Apps as it should be. Finally.

Thanks so much, Ghot.

Good job.

Mortiferon said:

Uh-oh? I now have seven logs for:

All dated 2/1/2022...
1:05:29 AM
1:17:25 AM
10:25:58 AM
2:40:13 PM
3:16:54 PM
3:41:24 PM
4:21:12 PM

Event 11308, MsiInstaller
Product: AMD PCI Driver -- Error 1308.Source file not found: C:\AMD\Chipset_Software\Packages\IODriver\PCI\PCI Driver\WTx64\dpinst64.exe. Verify that the file exists and that you can access it.

And of course, I cannot, because it is not there. Cause for worry?

Am now also experiencing other issues (very, very slow File Explorer green loading bar kind of stuff; hadn't been happening before. Debating on another topic for that and potentially related errors I've uncovered. Like, apparently, AMD Ryzen doesn't like WD HDD's? ).

2/1/2022 was when you were trying to install the chipset driver and it was failing.

I have two WD drives with my Ryzen CPU... no problems.

You post #22, when you solved the problem, was at 7:45 PM.
All those times, in post #24, are before that time.

All we need to care about is problems "after" 7:45 PM.
Here is a batch file that will clear Event Viewer. Then you can see what errors you're getting... now.


Clear All Event Logs in Event Viewer in Windows

No. Something is really, really, really wrong now. File Explorer wasn't working (first ever), not displaying icons before it quit doing anything (wouldn't show "My PC", waited several minutes and wouldn't). And when I restarted, I was forced to change my PIN ("Your organization requires that you change your PIN"), despite that the Group Policy is as it should be (Pin Complexity - Not configured; PIN expiration = 0).

Prior to this now absolutely ridiculous situation over these drivers, this system had been flawless.

To underscore the problem with File Explorer, it is running worse than System Two (8 years, on an HDD primary). Not OK.

But I am MOST alarmed by being *forced* to change my PIN over apparently a ghost prompt. What is this, do you know? It shouldn't be doing this, given the Group Policy as it is???

Edit: System Two had been Win7 Pro and has been Win10 Pro all those 8 years and never, not once, have I ever been forced to change Password or PIN. I'm really freaking out right now. Any information?

Mortiferon said:

No. Something is really, really, really wrong now. File Explorer wasn't working (first ever), not displaying icons before it quit doing anything (wouldn't show "My PC", waited several minutes and wouldn't). And when I restarted, I was forced to change my PIN ("Your organization requires that you change your PIN"), despite that the Group Policy is as it should be (Pin Complexity - Not configured; PIN expiration = 0).

Prior to this now absolutely ridiculous situation over these drivers, this system had been flawless.

To underscore the problem with File Explorer, it is running worse than System Two (8 years, on an HDD primary). Not OK.

But I am MOST alarmed by being *forced* to change my PIN over apparently a ghost prompt. What is this, do you know? It shouldn't be doing this, given the Group Policy as it is???

Edit: System Two had been Win7 Pro and has been Win10 Pro all those 8 years and never, not once, have I ever been forced to change Password or PIN. I'm really freaking out right now. Any information?

I remember someone else having a similar problem... being forced to change PIN.
I don't remember where it was, or the solution. It was about 1-2 months ago.

I would make a new topic titled: Your organization requires that you change your PIN ??

...and then post the problems you're having.

When you describe the problems, describe them in this order...

1. The PIN problem
2. The File Explorer problem.
3. That you just updated your chipset driver.

I can't really help with this... because... I don't have an MS account, I don't use a PIN, and I'm on Windows Home (no group policy editor). :/

And don't "freak out".