Code 39 Sound drivers

[alexsmith2709]

I've got a windows 10 laptop here with no sound. Windows tells me that no audio devices are installed and in device manager i have yellow exclamations next to the sound driver. It has a realtek and Intel audio driver as well as Microsoft Streaming Proxy which i've not seen before. In device manager it gives me a code 39 error and "windows cannot load the device driver for this hardware. the driver may be corrupted or missing"
I have tried uninstalling and deleting the driver and reinstalling but the same happens. I have also tried installing the driver using SDIO with no luck either way.

Any ideas?

 

[Mick]

Is the VSS service running? I'd be inclined to try a quick system restore on the grounds that it can't make things worse

 

[MichaelBits]

Perhaps try and boot into linux and see if you have sound.
The device itself could be bad which is why no driver will work.

 

[GreyWolf]

Laptop model and series please? Also give driverscloud.com a scan might find the driver you need, depending on what model it is it may just used to have compatibility drivers on it only.

 

[Diggs]

Hmmm... I'm picking up a laptop tomorrow that has Realtek sound. The owner says every time they listen to streaming radio it locks the system up tight and requires a hard (6-second) shutdown.

 

[GreyWolf]

Yup definitely looks like a pattern did a google lookup for the past month seems we're not the only ones... looks like a previous driver version would be more adequate.
https://www.tenforums.com/sound-audio/5993-latest-realtek-hd-audio-driver-version-253.html

 

[alexsmith2709]

It appears the driver doesnt install properly with SDIO as if i start it again it still says that driver needs updating. No joy with driverscloud.
No system restore points, its turned off (surprise surprise!).
Looks like i'll go hunting for an older version to see if that works as there is no roll back option

 

[GreyWolf]

https://github.com/alanfox2000/realtek-hda-release/releases/

 

[alexsmith2709]

Thanks for the github link, very useful for future but when i try the latest drivers on there for samsung (its a samsung laptop) it says no driver package supported.

 

[NJW]

As you're in the UK, I imagine that this is an older Samsung laptop, almost certainly pre-2015 (when Samsung stopped selling laptops in Europe) and almost certainly not officially supported for Windows 10. On top of that, Samsung (in my experience) did some pretty whacky things with not-quite-standard hardware.

So, I'd suggest looking on the Samsung support site and getting the last available sound driver from there. If it's for Windows 8, it may Just Work with Windows 10 (but could break with future W10 updates); if it's older than Windows 8, try installing in compatibility mode.

The Intel sound that you mention will be for HDMI video output, so probably less important (though probably easier to get working, if it isn't already). Windows will ignore sound hardware that isn't connected to anything, so you'll need to plug in an HDMI monitor with sound (e.g., HDMI television) to test the Intel sound.

Edit to add: a cheap USB sound adapter may be the price of running Windows 10 on this machine.

 

[alexsmith2709]

None of these suggestions fixed it. I did an in-place upgrade to reinstall 1809 and now i have sound again

 

[alexsmith2709]

I got another one of these in yesterday, quite an old Sony Vaio. Its got 1803 installed. Tried all the previous suggestions and also a in-place upgrade of 1803 with no joy, i tried installed 1809 but it wont saying drivers are incompatible.
As before, no system restore, only updates listed are for office, also tried going back to previous build (did this before i reinstalled 1803) and it goes through the process but 1803 is still installed, i guess 1803 was installed more than a month ago.

Any other suggestions or a way of forcing 1809 to install?

 

[Diggs]

Any other suggestions or a way of forcing 1809 to install?

Have you tried forcing 1903 on it?

https://www.microsoft.com/en-us/software-download/windows10

 

[Sky-Knight]

I hate Sony... they used custom hardware ID's so the only "fix" for stuff like this is usually manually hacking their hardware ID into the appropriate driver's INI file, and that driver will require manual updates for the rest of time.

The driver that's at fault likely came from Win7, a fresh Win10 install will probably work and whatever device is borked won't "work" after the install, but at least then you know what driver to hack up.

 

[NJW]

Everything I said about Samsung (upthread) applies to Sony!

The bottom line is that some machines just won't run Windows 10. They're not even good candidates for Linux, though most of the fundamental hardware will work (usual problems are things like wireless switches and hotkeys beyond brightness and volume).

Edit: What about trying a sysprepped image? At least that should get you beyond the installer checks – probably as far as a BSOD ...

 

[alexsmith2709]

I hate Sony too, im trying to install 1903 now, its 33% of the way so hopefully it will complete and fix the issue...and not have other issues!

 

[alexsmith2709]

Installing 1903 worked from the iso and fixed the sound issue. Definitely need to start telling people with older equipment to go buy new stuff!

 

[Sky-Knight]

In this case it's less about new vs old, but proprietary vs open. The issue here is a list of hardware IDs that can be supported by reference drivers, but aren't because Sony decided to customize junk and then drop support. Because of this, some manufacturers require a nuke and pave to clear the old specific drivers to make room for the more broadly matched generic drivers, IF they match. Sometimes you have to hack up an INF file to make them match. Giant mess.