Realtek HD Audio Driver Version old post

wiggly1uk2000 said:

Since Realtek's FTP site disappeared I (like many others I'm sure) have been using the Windows Update Catalog to track development of the Realtek High Definition audio driver. On a couple of occasions I've noticed that CAB files for a particular release have changed over time. The latest release (8029) is a good example. I downloaded this as soon as I saw it and my CAB filename was this:

312dab0c-4146-434c-8530-3cf03064e06a_864a79a7ecf81dc0d0f882892d2dd9fa2aca1f4f.cab

Then, the next day I checked again and it had changed to this:

4bbf4a99-74a3-4163-91fb-db3d585440a0_3effc5fa3eb35d40a07a57221d5ae8dc7d1cd5b0.cab

This is for the exact same 8029 (x64) driver release. What's more the CAB contents have changed too. The original version worked fine on my system and does not have the missing mbfilt64.sys file that I mentioned in an earlier post. The revised version has that file omitted and other changes too, including to INF files themselves.

I'm trying to understand how WIndows Update Catalog works and why these changes are occurring after a driver has been released to the catalog. Any ideas?

In the meantime I'll keep watching in case the CAB file for 8029 changes again! It will help these cold, winter days to fly by.

I have no idea what the logic behind the changes is...
before one could simply type "Realtek Audio" or "Realtek HD Audio" and you'd get all the updates, including the latest ones.
Now it really is, at least for me, a matter of being lucky with your searches.
Anyhow, thanks for the update, and thanks to Brink as well!

asturias7 said:

I have no idea what the logic behind the changes is...
before one could simply type "Realtek Audio" or "Realtek HD Audio" and you'd get all the updates, including the latest ones.
Now it really is, at least for me, a matter of being lucky with your searches.
Anyhow, thanks for the update, and thanks to Brink as well!

Yes, each new driver release is a bit of a lucky dip! It adds to the fun I suppose!

No fun if you have to go through 10s of pages to find anything new (this is when searching for "realtek" only, adding more keywords gives more results). Keywords should restrict the results (logical AND) not multiply them (logical OR).

spapakons said:

No fun if you have to go through 10s of pages to find anything new (this is when searching for "realtek" only, adding more keywords gives more results). Keywords should restrict the results (logical AND) not multiply them (logical OR).

On the Windows Update Catalog I search for Realtek High Definition and then sort by version.

wiggly1uk2000 said:

<snip>I'm trying to understand how WIndows Update Catalog works and why these changes are occurring after a driver has been released to the catalog. Any ideas?

In the meantime I'll keep watching in case the CAB file for 8029 changes again! It will help these cold, winter days to fly by.

IntelliMoo said:

I always thought the .cab file names just change periodically to prevent sites from hot-linking or whatever, but not sure. As for the actual contents changing, good question there.

I'm guessing the .cab file name is a hash checksum MS calculates for the .cab. You can be guaranteed it's unique and will change when anything is changed in the cab, even if minor like a comment

@wiggly1uk2000
Again, great work in noticing the cab filename change! That's a great find!

I don't know how the MUC release process works but it's clear MS allows (minor?) tweaks to a release even after its published.

Lesson learned, it's a good reason to note and track the cab filename installed. It's another reason 2 different people get somewhat different results with the "same" release. Knowing both release # and cab filename could be helpful for when someones helping debug

Installs of the newer ones just throw errors when trying to install.

Have you tried the driver from the vendor. Doesn't look like your m/b uses Realtek chip (scroll down to see)

/* EDIT */
Can have a look at what you DO have and what might be going on

/* EDIT 2*/
Given the circumstance would be better you started a new and separate thread for help as doesn't look Realtek related. You post the link to new thread here but put output of info requested in new thread

List any Problem devices

• Make sure devices are connected and powered on
• Click the Start Orb, type msinfo32 in the search box. Hit Enter
• Click the + sign next to Components to expand it
• Click Problem Devices. Anything appear?
• If yes, click on it, Ctrl-A to select all, Ctrl-C to copy it, Ctrl-V to paste into next post
• On the other hand, if no devices are listed, tell me so

Generate and attach a DirectX report

• Click Start, enter dxdiag in the search box
• When DxDiag opens, look along the buttons at the bottom of the DxDiag window===> If you’re running 64 bit Windows, you’ll see a 64-bit DxDiag button. Click it to run the 64-bit version of dxdiag
• Notice progress in lower left window corner
• When done, click Save Information button and save as a text file to your Desktop
• Upload the file to your next post

I just wanted to say that 6.0.1.8029 sounds better on my system than 8023.