Recommended Posts

Ok guys I just installed Windows 8 RTM (fresh install) and I have no sound. I have made sure the drivers are installed, checked the Windows services and ran a cmd prompt "fix" all with no luck. I have uninstalled and installed the driver several times and the everything shows it should be working but I have no sound in anything and I am at a loss... It worked in all the previous builds but now it does not work in RTM. My laptop is a Compaq CQ60-211DX and I recently upgraded the CPU and Memory, I don't know what else to do and I am pretty upset because I am really liking Windows 8.

Does anyone have any solutions?

EDIT: When the sound driver is installed video playback via youtube or any other videos is in slow motion. Once the drivers are removed it plays smooth...

Link to comment
https://www.neowin.net/forum/topic/1099439-no-sound-in-rtm/
Share on other sites

I am amazed I am not able to find any solutions, kind of a fail on Microsoft's part... Installs drivers that don't even work and when the drivers are installed the video playback is in slow motion. I really hope this is fixed when it hits retail.

Ok guys I just installed Windows 8 RTM (fresh install) and I have no sound. I have made sure the drivers are installed, checked the Windows services and ran a cmd prompt "fix" all with no luck. I have uninstalled and installed the driver several times and the everything shows it should be working but I have no sound in anything and I am at a loss... It worked in all the previous builds but now it does not work in RTM. My laptop is a Compaq CQ60-211DX and I recently upgraded the CPU and Memory, I don't know what else to do and I am pretty upset because I am really liking Windows 8.

Does anyone have any solutions?

EDIT: When the sound driver is installed video playback via youtube or any other videos is in slow motion. Once the drivers are removed it plays smooth...

Did you install the latest driver for it?

http://drivers.softp...ows-8-x64.shtml

A buddy of mine had the same issue. I pointed him to that dl and it fixed his issue.

I am amazed I am not able to find any solutions, kind of a fail on Microsoft's part... Installs drivers that don't even work and when the drivers are installed the video playback is in slow motion. I really hope this is fixed when it hits retail.

I have a Presario CQ60 212EM and sound worked out of the box with 8 RTM and all pre-release versions too, iirc I either used the Win 7 drivers or just let WU install/update them

Did you install the latest driver for it?

http://drivers.softp...ows-8-x64.shtml

A buddy of mine had the same issue. I pointed him to that dl and it fixed his issue.

Thanks, I will give that a try tonight. Not at home at the moment :) Just so I don't accidentally install it wrong what is the correct process on installing a .cab file?

I have a Presario CQ60 212EM and sound worked out of the box with 8 RTM and all pre-release versions too, iirc I either used the Win 7 drivers or just let WU install/update them

Worked find in all the previous versions except for RTM, going to try the drivers that Lo Tec posted and see what happens.

Thanks, I will give that a try tonight. Not at home at the moment :) Just so I don't accidentally install it wrong what is the correct process on installing a .cab file?

Worked find in all the previous versions except for RTM, going to try the drivers that Lo Tec posted and see what happens.

Here's the ones for mine (x64)

http://ftp.hp.com/pub/softpaq/sp45001-45500/sp45166.exe

I`ll run driver grabber for you and pull the ones that are running on mine if you still don't have it working

I would just open it with winrar and then point device manager to it or try running the .exe within.

CAB files are common to drivers Microsoft places on their os installation disks.

They are compressed files (similiar to zip) which contain several files and can even contain hundreds of driver files. You don't install a cab file. You install the device using the add new hardware program....... during hardware installation the system will automtically look for the installation disk from it's original install location. If the disk or files are not in that default location, then you must redirect it to where the driver.cab file is located. The installation will automatically look for the required file(s) within the cab file and extract from it what is needed.

Source

Here's all the Audio related drivers from my CQ60, extract and use Device Manager to install manually

http://localhostr.com/files/bCuoSnq/Compaq%20Presario%20CQ60%20Notebook%20PC%2019-08-2012%2002-30-16.zip

You have installed the Chipset drivers right ? (Compatibility mode for 7)

Here's all the Audio related drivers from my CQ60, extract and use Device Manager to install manually

http://localhostr.co...%2002-30-16.zip

You have installed the Chipset drivers right ? (Compatibility mode for 7)

Thanks, creating a windows 7 backup now and going to try it again.

Well no luck with anything... I tried both of the drivers you guys posted and the one you posted Lo Tec did not work, it says the Windows drivers are the most recent and it wont allow me to install them.

Well no luck with anything... I tried both of the drivers you guys posted and the one you posted Lo Tec did not work, it says the Windows drivers are the most recent and it wont allow me to install them.

Very weird, if you haven't already got it setup the way you want I would try reinstalling 8 from scratch, I find it unlikely that everything would work in the pre-release versions, and everything works on my CQ60, but not in RTM for yours, audio driver seems the same although your chipset is Intel vs nVidia for mine

Are you running the latest BIOS ?

Very weird, if you haven't already got it setup the way you want I would try reinstalling 8 from scratch, I find it unlikely that everything would work in the pre-release versions, and everything works on my CQ60, but not in RTM for yours, audio driver seems the same although your chipset is Intel vs nVidia for mine

Are you running the latest BIOS ?

Yup everything is updated to the latest. I am going to hold out and see if the retail version fixes the problem via updates, if it doesn't I may be getting a new laptop with my left over pell grant :p

  • 2 months later...

Well I just installed the retail version and installed the updated driver via Windows Update and it is still borked... How can this be? This is a very common audio device and I don't understand why it does not work. Has anyone else had this problem? Kind of ****ed I paid for Windows and now I can't really use it because there is no sound...

NoLimit, go in Services and make sure the Windows Audio service is running and set to Automatic.

Then, go in the volume controls and make sure its not muted. I know, it's stupid -- but you never know.

Then, go in your Audio devices (Right-click on the speaker in your tray) and click on Playback devices

Make sure the right playback device is set as default. It sometimes moves around.

NoLimit, go in Services and make sure the Windows Audio service is running and set to Automatic.

Then, go in the volume controls and make sure its not muted. I know, it's stupid -- but you never know.

Then, go in your Audio devices (Right-click on the speaker in your tray) and click on Playback devices

Make sure the right playback device is set as default. It sometimes moves around.

Still no luck... I really don't know what to do. :angry:

Is there a key on your laptop that turns the sound on-off ? Worth a shot .

Nope, I have muted,unmuted, uninstalled and reinstalled and no luck. Everything shows as working, no red x's or anything. Makes not a damn bit of sense....

This topic is now closed to further replies.
  • Posts

    • With the current hardware prices Microsoft should lift the restriction. Then if you have the correct TPM then allow you to use X feature, if you don't have the correct TPM then don't but still actually let you run windows. 11. With a disclaimer during install that X features would be unavailable.
    • It's good for recycling of course. But commence inflation of a second hand RAM bubble and price gouging on DDR 4 inventory in 3... 2... 1...
    • Bypassed Windows 11 shows surprising stability on ancient, completely unsupported hardware by Sayan Sen When Windows 11 was first released, one of the most complained-about issues with the new desktop Microsoft OS was its higher system requirements, which pushed many relatively modern and powerful processors and devices onto the officially unsupported list. Thankfully, they have not been updated again for the base OS, though systems require four times the memory and storage if they want to run AI-powered apps and features. As such, Windows 11 technically runs on 4GB of memory, and there is no imposed restriction on the generation of memory it supports. Speaking of memory, prices are extremely high nowadays for hardware, especially DDR5 and DDR4 kits due to the current silicon shortage, and there are also reports of it affecting DDR2 as well, and it might only be a matter of time before even DDR1 gets affected. Before that could happen, an enthusiast took an ancient DDR1-based system and decided to try out Windows 11 on it to see how well the modern OS would fare on such hardware. The system runs an outdated graphics card interface standard based on AGP, or Advanced Graphics Port, called AGP 3.0 or AGP8x. AGP was essentially succeeded by the modern PCI Express (PCIe) bus standard. The user behind the experiment is retro hardware enthusiast Omores, who built the system around an ASRock ConRoe865PE motherboard based on Intel's i865PE chipset from way back in 2003, around the time when AGP was still in fashion. What made this board special back in the day was its unusual support for newer Core 2 Duo and even Core 2 Quad processors while still retaining older DDR1 memory support and an AGP8X graphics slot, making it an ideal bridge or link between two vastly different generations. Powering the machine was Intel's Core 2 Quad Q6600 alongside 3GB of DDR1 RAM and an ATI Radeon HD 4650 AGP graphics card, one of the final and most capable GPUs released for the aging AGP interface. While installing Windows 11 itself was relatively easy by bypassing Microsoft's hardware checks, getting the graphics card fully functional proved to be some challenge. Microsoft had quietly dropped native AGP support after the earliest releases of Windows 10, meaning newer versions of Windows no longer include the necessary Graphics Address Remapping Table (GART) drivers required for proper AGP acceleration. Without them, AGP graphics cards typically boot up, though with limited functionality, and can often throw a Code 43 error in Device Manager. To work around the limitation, Omores extracted Intel's legacy AGP440 SYS driver from an early Windows 10 release and paired it with a modified INF file so Windows 11 would correctly recognize the chipset. Following this and combined with AMD's final 64-bit Catalyst AGP drivers from 2012, the Radeon HD 4650 was able to operate with full AGP 8X acceleration intact. The result was said to be surprisingly usable for hardware that is over two decades old. Hardware-accelerated H.264 video playback worked correctly and benefited apps like Firefox, while legacy applications and games ran without major graphical issues. The system also successfully completed the 3DMark 2001 benchmark, although performance naturally lagged behind what the same hardware achieves under Windows 7, which is significantly lighter than Windows 11. There was, however, one unavoidable limitation as Microsoft's Windows 11 version 24H2 introduces a mandatory SSE4.2 CPU instruction requirement that cannot be bypassed through installer modifications or registry tweaks. Since no AGP-era processor supports SSE4.2, Windows 11 version 23H2 effectively becomes the final release capable of running on such systems. Regardless, it is still a very cool feat and quite fascinating to see just how stable Windows 11 turned out to be on such unfamiliar hardware. Source: Omores (Patreon) via O_MORES (Reddit)
    • That will only really help other players that are also responsible for creating the problem.
    • Well, it's good to know that they have found a workaround to a problem that they helped create, I guess...
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      538
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!