Mazafromavignon

Q: No audio : Windows 10 Bootcamp

Hi everybody. I begin to apologise because I'm french and my english is not perfect.

 

So, you are, the apple community, my last chance.

 

First of all : I give you my set up, that will be usefull.

Config : Macbook pro late 2011

Upgrade with SSD 850 evo

So I have 1 HD and 1 SSD.

 

I recently instaled Windows 10 with Bootcamp on the Hard Disk. Everything works well, but I don't have audio.

I had installed the latest Bootcamp (Drivers) on Windows 10. But at this point I had no audio.

 

I saw on "device manager" that the "Hight Definition audio codec" is installed, but badly. I can see a Yellow exclamation mark and an error in the property (Code 10).

 

Then, I tried to uninstall this Driver (directly in the device Manager), to install it better. But nothing looks work.

I had also tried to download directly the latest driver on the Realtek Website.

 

I have more information for you : If I plug a jack I have the same issue.

In the Mac partition : The latest OS Yosemite is installed

When I installed W10, it was on an empty partition, with a boutable USB drive.

I tried the latest Bootcamp and also 5.1.5626

 

I really hope that you'll can help me.

Thank You

MacBook Pro, Other OS, Windows 10

Posted on Aug 4, 2015 8:55 PM

Close

Q: No audio : Windows 10 Bootcamp

  • All replies
  • Helpful answers

first Previous Page 3 of 4 last Next
  • by Mazafromavignon,

    Mazafromavignon Mazafromavignon Aug 5, 2015 4:38 PM in response to Mazafromavignon
    Level 1 (0 points)
    Aug 5, 2015 4:38 PM in response to Mazafromavignon

    Now the sound dont work on my mac.. I have a forbiden sign.

  • by Loner T,

    Loner T Loner T Aug 5, 2015 5:40 PM in response to Mazafromavignon
    Level 7 (23,663 points)
    Safari
    Aug 5, 2015 5:40 PM in response to Mazafromavignon

    Did your Windows installation complete successfully and were you able to create an account?

     

    Did you pick the correct partition to install Windows. Disk0/Partition 4?

  • by Eric Landry,

    Eric Landry Eric Landry Aug 6, 2015 4:49 PM in response to Loner T
    Level 1 (10 points)
    Aug 6, 2015 4:49 PM in response to Loner T

    Here, from my MBP 13" early 2011

     

    LegacyBios.PNG

  • by Loner T,

    Loner T Loner T Aug 6, 2015 5:07 PM in response to Eric Landry
    Level 7 (23,663 points)
    Safari
    Aug 6, 2015 5:07 PM in response to Eric Landry

    Eric Landry wrote:

     

    Here, from my MBP 13" early 2011

     

    LegacyBios.PNG

    Pardon my confusion. Did you change you screen name, or is this a new issue?

  • by Eric Landry,

    Eric Landry Eric Landry Aug 6, 2015 5:12 PM in response to Loner T
    Level 1 (10 points)
    Aug 6, 2015 5:12 PM in response to Loner T

    hmmm, I posted a reply on this guy's post on Aug 5, 2015 9:57 AM to share how I got Windows 10 to work with sound on my early 2011 mbp, and you reply on my post instead his, so I thought you wanted a screenshot of my install..

  • by Loner T,

    Loner T Loner T Aug 6, 2015 6:00 PM in response to Eric Landry
    Level 7 (23,663 points)
    Safari
    Aug 6, 2015 6:00 PM in response to Eric Landry

    Now it makes more sense. Thanks for confirming what I think is the root cause. The challenge with the OP is that configuration has two disks. If the original configuration was intact, it would be a legacy BIOS install. The second disk complicates the installation and hence is compounding the EFI vs BIOS selection.

  • by Mazafromavignon,Solvedanswer

    Mazafromavignon Mazafromavignon Aug 17, 2015 3:09 PM in response to Loner T
    Level 1 (0 points)
    Aug 17, 2015 3:09 PM in response to Loner T

    I was not available, sorry.

    Ok at the end, I had the same answer than you. I found that the only problem was that I had two disks. I finally decided to forget W10. It was too many problems.

    Thank you very much for your help

  • by Loner T,

    Loner T Loner T Aug 17, 2015 5:52 PM in response to Mazafromavignon
    Level 7 (23,663 points)
    Safari
    Aug 17, 2015 5:52 PM in response to Mazafromavignon

    You can try the W10 upgrade if you can remove one of the drives that will not be upgraded.

  • by dlralban,

    dlralban dlralban Aug 24, 2015 10:38 PM in response to Eric Landry
    Level 1 (0 points)
    Aug 24, 2015 10:38 PM in response to Eric Landry

    Bonjour Eric,

     

    Je n'ai pas réussi à retrouver ton post initial où tu expliques comment tu as réussi ton install de Windows 10 sur MB Pro early 2011 avec le son qui fonctionne.

     

    J'ai installé Windows 10 64 bits mon mon MacBook Pro (j'ai le même modèle que le tien) de la façon suivante :

    - création du disque d'install usb en utilisant Bootcamp (que j'ai modifié pour rendre cette install possible sur ma config normalement non autorisée)

    - suppression de la partition créée par Bootcamp (qui était en MBR et donc incompatible avec Windows 10)

    - création d'une partition NTFS en GPT à partir de l'interface d'installation de Windows 10

    - installation de Windows 10

     

    L'audio ne fonctionne pas...

     

    Quelle procédure me conseilles tu de suivre ?

     

    Merci beaucoup,

     

    Alban

    dlralban@gmail.com

  • by Mazafromavignon,

    Mazafromavignon Mazafromavignon Aug 25, 2015 4:39 AM in response to dlralban
    Level 1 (0 points)
    Aug 25, 2015 4:39 AM in response to dlralban

    Bonjour Eric,

    L'installation de Windows 10 a été un échec pour moi. Je n'ai pas réussi à avoir le son. Toutes les procédures que j'ai tenté, m'ont amené à re-formater mon Mac.

    Les problèmes que j'ai rencontré étaient les suivant : - Installation propre de W10 (comme vous) en convertissant la partition en GPT via l'installateur W10. Mais pas de son une fois l'OS installé

     

    - Ou installation via BootCamp : Echec de l'installation, impossible de réatribuer la partition. Je me retrouvais avec des espaces vides.

     

    Avec l'arrivée de l'OS El capitain, j'ai finalement laissé tombé Windows 10.

    De toute manière je crois que j'ai voulu l'installé à cause de l'euphorie de sa sortie. Dans le fond, il n'a rien de plus mis à part cortana.

     

    J'ai essayé l'installation via parallèle, elle se déroule très bien.

    J'espère que m'a réponse vous aura était utile.

    Cordialement 

  • by Mazafromavignon,

    Mazafromavignon Mazafromavignon Aug 25, 2015 4:44 AM in response to Mazafromavignon
    Level 1 (0 points)
    Aug 25, 2015 4:44 AM in response to Mazafromavignon

    Ps : j'ai remarqué que les drivers audio de Bootcamp étaient différents de ceux de Parallèle. Je n'ai pas essayé, mais il y a une probabilité pour que ca marche. J'espère que cette piste vous aidera.

  • by Loner T,Helpful

    Loner T Loner T Aug 25, 2015 4:47 AM in response to dlralban
    Level 7 (23,663 points)
    Safari
    Aug 25, 2015 4:47 AM in response to dlralban

    Your Mac (as well as Mazafromavignon 's Mac) is a preUEFI Mac. Modifying Bootcamp info.plist causes problems, including GPT vs MBR, black screens, audio issues and GPU issues, etc. You need to install using regular BIOS/MBR (not GPT) and a physical DVD (without modifying the info.plist). A Physical DVD is required for all Macs (except a few 2012 models) if they have a built-in Optical drive.

  • by Mazafromavignon,

    Mazafromavignon Mazafromavignon Aug 25, 2015 4:47 AM in response to Mazafromavignon
    Level 1 (0 points)
    Aug 25, 2015 4:47 AM in response to Mazafromavignon

    Ceux de Parallele s'appelle : AMD Driver update for AMD 8111 AC 97 Audio controller driver,

     

    Si il vous prend l'envie d'essayer tenez moi au courant, je suis curieux de voir si cela marche.

     

    Merci

  • by Mazafromavignon,

    Mazafromavignon Mazafromavignon Aug 25, 2015 4:50 AM in response to Loner T
    Level 1 (0 points)
    Aug 25, 2015 4:50 AM in response to Loner T

    That is right Loner T

     

    But I'm just thinking. Why audio driver are different with parallele than Bootcamp? I dont really know if this driver can work, but try should be interesting.

  • by Loner T,

    Loner T Loner T Aug 25, 2015 5:01 AM in response to Mazafromavignon
    Level 7 (23,663 points)
    Safari
    Aug 25, 2015 5:01 AM in response to Mazafromavignon

    On preUEFI Macs, there are are two different layers before the OS and drivers that are important to understand. Macs have used EFI 1.1 for some time (since the switch to Intel and in some cases even before that). After Late 2013, Mac switched to UEFI which is EFI 2.x. This changes the way hardware is exposed to OS and drivers. The EFI 1.1 layer starts a BIOS emulation layer called CSM-BIOS. Apple controls what devices are shown through this emulation layer to the OS and drivers. In UEFI mode, the firmware exposes the same devices to any OS which is installed. In your specific model of Mac, the sound devices are exposed through the CSM-BIOS layer, not through the EFI layer. If you use EFI Boot, you cannot see audio devices, GPUs have similar issues.

     

    Parallels (and other VMs) run their down BIOS on top of EFI (similar to Apple's). Parallels is seeing and accessing devices through the OS X layer, not through Windows. Most of the devices in Parallels Device Manager are 'virtual' devices that map to 'real' devices exposed by OS that Parallels is running on.

first Previous Page 3 of 4 last Next