![]() Let’s just say this took place over a ten-day period, during which I made at least a half-dozen attempted fixes before finally getting things figured out. What my story doesn’t really cover is the number of tries, and the amount of time I spent noodling around, trying to restore my UAD driver capability. Only the first two items in this short list of Realtek UAD Software Components need to (or can) be updated. Both updates proceeded to a successful conclusion, after which I was indeed able to run and use the Realtek Audio Control. Remembering that two of the three Realtek items under the “Software Components” heading also needed updating the last time I went through a similar exercise (see screencap following), I used the Update driver function in Device Manager for the “Realtek Audio Effects Component” and the “Realtek Audio Universal Service” under that heading, pointed at the same folder hierarchy. This worked with the audio, but I still couldn’t access the Realtek Audio Control. This time, when I went poking around in its WIN64 folders, I found an item named HDXAsrok.inf that I force-installed instead. This led me to a search of the Asrock website, where I found a link to a UAD driver set for vesion 8940. In fact, it displayed the same “Unable to access RDP server” error that it showed when I had mistakenly replaced the UAD driver with its (incompatible) HDA counterpart in the first place. I also knew things weren’t completely kosher or copacetic because the Realtek Audio Control (the UWP app that manages the UAD driver’s settings and capabilities) wouldn’t open. When I force-installed the generic version of that driver - simply named HDXRT.inf - and then saw the “Realtek(R) Audio” string under Device Manager’s “Sound, video and game controllers” heading, I knew I was on the right track. But when I looked back at the 8501 driver collection for UAD, I noticed the string HDX kept occurring in the various inf files for that driver targeted across a broad range of platforms in its WIN64 environment. inf file to point to inside Device Manager’s manual installation facility through “Have Disk” to MAKE it overwrite the HDA driver with its UAD equivalent. That’s because, try as I might, I couldn’t figure out which. It’s a good thing I’m a packrat, because I had to go back to the 8501 version of the drivers to successfully identify the UAD driver’s naming convention. A Return to UAD Requires Identifying, then Force-Installing the Right Driver In contrast, the other version reads “Realtek High Definition Audio” in this place. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |